[Python-checkins] r53085 - peps/trunk/pep-3000.txt

[guido.van.rossum]

Author: guido.van.rossum
Date: Tue Dec 19 22:17:06 2006
New Revision: 53085

Modified:
   peps/trunk/pep-3000.txt
Log:
Updated timeline.


Modified: peps/trunk/pep-3000.txt
==============================================================================
--- peps/trunk/pep-3000.txt	(original)
+++ peps/trunk/pep-3000.txt	Tue Dec 19 22:17:06 2006
@@ -48,10 +48,13 @@
 Timeline
 ========
 
-We need a meta-PEP for the Python 3000 timeline.  At this moment, I
-hope to have a first alpha release out sometime in 2007; it may take
-another year after that (or more) before the first proper release,
-named Python 3.0.
+I no longer think we need a meta-PEP for the Python 3000 timeline;
+instead, here's my current proposal.  I hope to have a first alpha
+release (3.0a1) out in the first half of 2007; it should take no more
+than a year from then before the first proper release, named Python
+3.0.  I would like all PEPs for features going into Python 3000 to be
+submitted by the end of April 2007 (allowing time for discussion and
+implementation after the initial submission).
 
 I expect that there will be parallel Python 2.x and 3.x releases for
 some time; the Python 2.x releases will continue for a longer time
@@ -63,9 +66,9 @@
 continued 2.x support, acceptance and stability of 3.0, and volunteer
 stamina.
 
-It's quite possible that Python 3.1 and 3.2 will be released much
-sooner after 3.0 than has been customary for the 2.x series.  The 3.x
-release pattern will stabilize once the community is happy with 3.x.
+I expect that Python 3.1 and 3.2 will be released much sooner after
+3.0 than has been customary for the 2.x series.  The 3.x release
+pattern will stabilize once the community is happy with 3.x.
 
 
 Compatibility and Transition