[Python-Dev] 2.7/3.2 release schedule (original) (raw)

Guido van Rossum guido at python.org
Tue Nov 10 16:55:11 CET 2009

On Tue, Nov 10, 2009 at 5:13 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

Arfrever Frehtes Taifersar Arahesis wrote:

2009-11-02 21:00 Benjamin Peterson <benjamin at python.org> napisał(a):

I've updated PEP 373 with my proposed release schedule:

- 2.7/3.2 alpha 1 2009-12-05 - 2.7/3.2 alpha 2 2010-01-09 - 2.7/3.2 alpha 3 2010-02-06 - 2.7/3.2 alpha 4 2010-03-06 - 2.7/3.2 beta 1 2010-04-03 - 2.7/3.2 beta 2 2010-05-01 - 2.7/3.2 rc1 2010-05-29 - 2.7/3.2 rc2 2010-06-12 - 2.7/3.2 final 2010-06-26 PEP 3003 states that Python 3.2 will be released 18-24 months after Python 3.1. Python 3.1 was released on June 2009-06-27 [1], so theoretically Python 3.2 should be released not before 2010-12-19 [2]. The PEP 3003 text isn't allowing for the fact that 3.1 is "3.0 as it should have been", so the starting point for the 18-24 month rule of thumb is actually back when 3.0 was released in Dec 2008. This was discussed a fair bit back when the decision was made to do the short release cycle between 3.0 and 3.1 in order to address some of the more glaring shortcomings of the 3.0 release.

Was this discussed somewhere? When I agreed to an early 3.1 release (or did I propose it?) I'm quite sure that I expected 3.2 to come the usual time (i.e., 18-24 months) after 3.1. I think I said something to the extent of "we'll treat 3.1 the same way we treat any release" which IMO implies a lifetime of 18-24 months.

-- --Guido van Rossum (python.org/~guido)

More information about the Python-Dev mailing list