iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update release dates and sub-release managers.

This commit is contained in:
Barry Warsaw 2008-03-18 00:22:23 +00:00
parent 4cc04f5f58
commit 26cbf3b37a
1 changed files with 23 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
pep-0361.txt
View File

@ -2,13 +2,13 @@ PEP: 361
Title: Python 2.6 and 3.0 Release Schedule Title: Python 2.6 and 3.0 Release Schedule
Version: $Revision$ Version: $Revision$
Last-Modified: $Date$ Last-Modified: $Date$
Author: Neal Norwitz Author: Neal Norwitz, Barry Warsaw
Status: Draft Status: Draft
Type: Informational Type: Informational
Created: 29-June-2006 Created: 29-June-2006
Python-Version: 2.6 Python-Version: 2.6
Python-Version: 3.0 Python-Version: 3.0
Post-History: Post-History: 17-Mar-2008
Abstract Abstract
@ -19,29 +19,30 @@ Abstract
release. release.
There will be at least two alpha releases, two beta releases, and 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 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 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 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 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. 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 We will be releasing Python 2.6 and 3.0 in lockstep, on a monthly
lockstep, on a monthly release cycle. The releases will happen on release cycle. The releases will happen on the first Wednesday of
the last Friday of every month. If this schedule works well, we every month through the beta testing cycle. There will be two
will continue releasing in lockstep during the beta program. weeks between release candidates. The final releases of Python
2.6 and 3.0 will happen in lockstep.
Release Manager and Crew Release Manager and Crew
Barry Warsaw volunteered to be Release Manager. 2.6/3.0 Release Manager: Barry Warsaw
Windows installers: Martin v. Loewis
XXX is building the Windows installers, Mac installers: Ronald Oussoren
XXX is building the Mac installers, Documentation: Georg Brandl
XXX the doc packages and RPMs: Sean Reifschneider
XXX the RPMs.
Release Schedule Release Schedule
@ -50,11 +51,14 @@ Release Schedule
betas and release candidates will be determined as the release process betas and release candidates will be determined as the release process
unfolds. The minimal schedule is: unfolds. The minimal schedule is:
Feb 29 2008: Python 2.6a1 and 3.0a3 are released. Feb 29 2008: Python 2.6a1 and 3.0a3 are released
Mar 25 2008: next alpha releases planned Apr 02 2008: Python 2.6a2 and 3.0a4 planned
May 07 2008: Python 2.6a3 and 3.0a5 planned
Monthly releases for alphas are planned starting at the end of Feb 2008: Jun 04 2008: Python 2.6b1 and 3.0b1 planned
http://mail.python.org/pipermail/python-dev/2008-February/077125.html 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 Completed features for 3.0