update for new schedule

This commit is contained in:
Barry Warsaw 2008-09-12 12:59:14 +00:00
parent 16641f0658
commit 46a946992a
1 changed files with 12 additions and 10 deletions

View File

@ -19,8 +19,7 @@ Abstract
release.
There will be at least two alpha releases, two beta releases, and
one release candidate. The release date is planned for the
beginning of October, 2008.
one release candidate. The releases are planned for October 2008.
Python 2.6 is not only the next advancement in the Python 2
series, it is also a transitional release, helping developers
@ -29,11 +28,13 @@ Abstract
makes sense to release both versions in at the same time. The
precedence for this was set with the Python 1.6 and 2.0 release.
We will be releasing Python 2.6 and 3.0 in lockstep, on a monthly
release cycle. The releases will happen on the first Wednesday of
every month through the beta testing cycle. There will be two
weeks between release candidates. The final releases of Python
2.6 and 3.0 will happen in lockstep.
Until rc, we will be releasing Python 2.6 and 3.0 in lockstep, on
a monthly release cycle. The releases will happen on the first
Wednesday of every month through the beta testing cycle. Because
Python 2.6 is ready sooner, and because we have outside deadlines
we'd like to meet, we've decided to split the rc releases. Thus
Python 2.6 final is currently planned to come out two weeks before
Python 3.0 final.
Release Manager and Crew
@ -57,9 +58,10 @@ Release Schedule
Jun 18 2008: Python 2.6b1 and 3.0b1 are released
Jul 17 2008: Python 2.6b2 and 3.0b2 are released
Aug 20 2008: Python 2.6b3 and 3.0b3 are released
Sep 03 2008: Python 2.6rc1 and 3.0rc1 planned
Sep 17 2008: Python 2.6rc2 and 3.0rc2 planned
Oct 01 2008: Python 2.6 and 3.0 final planned
Sep 12 2008: Python 2.6rc1 planned
Sep 17 2008: Python 2.6rc2 and 3.0rc1 planned
Oct 01 2008: Python 2.6final and 3.0rc2 planned
Oct 15 2008: Python 3.0final planned
See the public `Google calendar`_