On Sat, Feb 14, 2009 at 12:29 PM, Benjamin Peterson <benjamin@python.org> wrote:
Here's a very tentative 3.1 release schedule.
Thanks! Glad you're taking your new role of release manager seriously and are starting to plan ahead.
3.1a1 March 7 (Saturday) 3.1a2 April 11 (Saturday) 3.1b1 May 2 (Saturday) 3.1b2 May 23 (Saturday) 3.1rc1 June 13 (Saturday) 3.1rc2 June 27 (Saturday)
And final release on...?
I'm interested in your feedback with regards to the amount of time in beta and RC phase. Do you think we need that much time? Otherwise, we could move the final release back sometime in mid June.
It's a bit hard to compare this to other release schedules because it's coming much sooner after 3.0. I would guess this means that not as much has changed, and so the schedule could conceivably more compressed. If you want to take beta seriously as a time of consolidation where no new features should be added and no API changes should take place, you might consider dropping one beta, since in practice it is often hard to keep developers from wanting to change stuff anyways. You might also want to collect a list of serious changes that you want in this release; I know I/O in C is on the list (and without it I wouldn't consider it worth releasing) but there may be others. The developers of such features ought to be on board with delivering their code before the first beta. -- --Guido van Rossum (home page: http://www.python.org/~guido/)