On Mon, Mar 15, 2010 at 3:04 AM, Nathan Kinsinger < [email protected]> wrote:
The 0.8 milestone is set for 2011? I'm assuming you mean 2010. Two weeks > seems a little short for testing unless your talking about a bleeding edge > only release. > Indeed! I'm guessing that's 2010. :) > Also, do you have a list of bug fix commits you intend for 0.7.2? Just > trying to get a jump on rebasing to the new master. > Starting with 0.7.2, let's set a date here on the mailing list, say March 19th, as the deadline for nominating patches for inclusion. That gives everyone a chance to email their patches to the list. Once the deadline is reached we could set aside another week to get the patches applied, bump the version number, update the release notes and the Sparkle feed and then upload the new release. Once it's out the door, we can start discussing the roadmap/timeline of the 0.8 release. Selection criteria for 0.7.2 should be based on impact. Only those fixes that are unlikely to cause unforeseen bugs and that require minimal testing should be accepted (since we aren't running a long testing window here). The main goal being to get a release out and hopefully bring people's attention back to the project. I like the idea of setting public deadlines on the mailing list for patch nomination and review. This gives everyone fair warning/chance to get involved and hopefully gives people enough time to work around their various commitments. It also encourages developers to come to the mailing list if they are interested in getting their work included. So if you have bug fixes or other simple patches that make sense for 0.7.2, now's the time to send them in! Kevin
