We have a backlog of mostly-minor fixes to 1.x unreleased. I think we're all agreed that the best way to deal with them is to roll a 1.6 release.
At the start of December, Bill suggested a 1.6 release in three days. That started a thread which never led to an actual release. I'd like to resurrect the issue, but with a more relaxed timetable to give us a deadline we can meet without drop-everything haste, and motivate myself to work to it. I'm going to suggest three phases to a release candidate: 1. Review. Determine list of showstoppers, and wishlist. 2. Fix. Freeze issues list and work through them. 3. Roll RC. I'm also going to suggest a hard cutoff for review as the end of this month. That gives folks time to review the codebase and revisit whatever's on your mind. I'll then suggest second week of April as a soft target for a release candidate, on the supposition that the wishlist (at least showstoppers) won't be extensive. We have apr/1.6/STATUS and apu/1.6/STATUS to track this. If anyone has sensitive security issues, there's also the pmc/security repo that's fallen into disuse of late. I'll be taking a trawl through bugzilla, and hacking on as much of this as I can. Thoughts? Objections? I expect some of you are way ahead of me here, but I need to post if I'm going to motivate myself to hack on it. -- Nick Kew
