Well, what with an increase in client work and a move halfway across the country (Somerville Mass to Murphysboro Illinois), I'm afraid I've fallen further behind on the issue queues for migrate, migrate_d2d, and wordpress_migrate. It's been a bit of struggle to triage the queues, so to somewhat automate the which-issue-to-work-on-next process, I'm reducing it to an algorithm (each step of which will be applied to migrate, migrate_d2d, and wordpress_migrate in that order).
- Bug reports with patches (needs review, rtbc), oldest to newest
- Other bug reports, oldest to newest
- Other issues with patches (needs review, rtbc), oldest to newest
- Triage of support requests to make sure no bugs are lurking there
At that point, I plan on cutting release candidates for all three modules. Hopefully at that point I'll be able to start doing a better job of responding to new issues as they come in. Hard to say when I'll have a chance to review and respond to older support and feature requests, though, it'll depend on my workload (but of course I'm not the only one in the community capable of helping out with support requests - hint hint). Thank you. Edit: Let's keep track of where I am... I'll also note that not all issues will necessarily get committed/closed, there will be some triage as I go along and not everything will make the cut for Migrate 2.6 and the corresponding migrate_d2d/wordpress_migrate releases.
Bug reports with patches, migrate Bug reports with patches, migrate_d2d Bug reports with patches, wordpress_migrate Other active bug reports, migrate Other active bug reports, migrate_d2d Other active bug reports, wordpress_migrate Other issues with patches, migrate Other issues with patches, migrate_d2d Other issues with patches, wordpress_migrate Triage of support requests, migrate Triage of support requests, migrate_d2d Triage of support requests, wordpress_migrate