Update release dates and sub-release managers.
This commit is contained in:
parent
4cc04f5f58
commit
26cbf3b37a
42
pep-0361.txt
42
pep-0361.txt
|
@ -2,13 +2,13 @@ PEP: 361
|
|||
Title: Python 2.6 and 3.0 Release Schedule
|
||||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Neal Norwitz
|
||||
Author: Neal Norwitz, Barry Warsaw
|
||||
Status: Draft
|
||||
Type: Informational
|
||||
Created: 29-June-2006
|
||||
Python-Version: 2.6
|
||||
Python-Version: 3.0
|
||||
Post-History:
|
||||
Post-History: 17-Mar-2008
|
||||
|
||||
Abstract
|
||||
|
||||
|
@ -19,29 +19,30 @@ Abstract
|
|||
release.
|
||||
|
||||
There will be at least two alpha releases, two beta releases, and
|
||||
one release candidate. The release date is planned to be in 2008.
|
||||
one release candidate. The release date is planned for the
|
||||
beginning of September, 2008.
|
||||
|
||||
Python 2.6 is not only the next advancement in the Python 2
|
||||
series, it is also a transitionary release, helping developers
|
||||
series, it is also a transitional release, helping developers
|
||||
begin to prepare their code for Python 3.0. As such, many
|
||||
features are being backported from Python 3.0 to 2.6. Thus, it
|
||||
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.
|
||||
|
||||
During the alpha test cycle we will be releasing both versions in
|
||||
lockstep, on a monthly release cycle. The releases will happen on
|
||||
the last Friday of every month. If this schedule works well, we
|
||||
will continue releasing in lockstep during the beta program.
|
||||
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.
|
||||
|
||||
|
||||
Release Manager and Crew
|
||||
|
||||
Barry Warsaw volunteered to be Release Manager.
|
||||
|
||||
XXX is building the Windows installers,
|
||||
XXX is building the Mac installers,
|
||||
XXX the doc packages and
|
||||
XXX the RPMs.
|
||||
2.6/3.0 Release Manager: Barry Warsaw
|
||||
Windows installers: Martin v. Loewis
|
||||
Mac installers: Ronald Oussoren
|
||||
Documentation: Georg Brandl
|
||||
RPMs: Sean Reifschneider
|
||||
|
||||
|
||||
Release Schedule
|
||||
|
@ -50,11 +51,14 @@ Release Schedule
|
|||
betas and release candidates will be determined as the release process
|
||||
unfolds. The minimal schedule is:
|
||||
|
||||
Feb 29 2008: Python 2.6a1 and 3.0a3 are released.
|
||||
Mar 25 2008: next alpha releases planned
|
||||
|
||||
Monthly releases for alphas are planned starting at the end of Feb 2008:
|
||||
http://mail.python.org/pipermail/python-dev/2008-February/077125.html
|
||||
Feb 29 2008: Python 2.6a1 and 3.0a3 are released
|
||||
Apr 02 2008: Python 2.6a2 and 3.0a4 planned
|
||||
May 07 2008: Python 2.6a3 and 3.0a5 planned
|
||||
Jun 04 2008: Python 2.6b1 and 3.0b1 planned
|
||||
Jul 02 2008: Python 2.6b2 and 3.0b2 planned
|
||||
Aug 06 2008: Python 2.6rc1 and 3.0rc1 planned
|
||||
Aug 20 2008: Python 2.6rc2 and 3.0rc2 planned
|
||||
Sep 03 2008: Python 2.6 and 3.0 final
|
||||
|
||||
|
||||
Completed features for 3.0
|
||||
|
|
Loading…
Reference in New Issue