Update as in the past tense, mark as final.

This commit is contained in:
Barry Warsaw 2001-12-24 20:58:36 +00:00
parent 451bb838de
commit bb14be0f41
1 changed files with 32 additions and 30 deletions

View File

@ -1,8 +1,8 @@
PEP: 251
Title: Python 2.2 Release Schedule
Version: $Revision$
Author: guido@python.org (Guido van Rossum), barry@zope.com (Barry A. Warsaw)
Status: Incomplete
Author: barry@zope.com (Barry A. Warsaw), guido@python.org (Guido van Rossum)
Status: Final
Type: Informational
Created: 17-Apr-2001
Python-Version: 2.2
@ -10,15 +10,14 @@ Post-History: 14-Aug-2001
Abstract
This document describes the post-Python 2.1 development and
release schedule. The schedule primarily concerns itself with
PEP-sized items. Small bug fixes and changes will occur up until
the first beta release.
This document describes the Python 2.2 development and release
schedule. The schedule primarily concerns itself with PEP-sized
items. Small bug fixes and changes will occur up until the first
beta release.
NOTE: the schedule below and the list of features under
consideration are all subject to change! If the energy in the
community changes or the feedback on a PEP is particularly
positive or negative, this may affect decisions.
The schedule below represents the actual release dates of Python
2.2. Note that any subsequent maintenance releases of Python 2.2
should be covered by separate PEPs.
Release Schedule
@ -26,8 +25,8 @@ Release Schedule
Tentative future release dates. Note that we've slipped this
compared to the schedule posted around the release of 2.2a1.
21-Dec-2001: 2.2 (final release)
14-Dec-2001: 2.2c1 [Released] (release candidate)
21-Dec-2001: 2.2 [Released] (final release)
14-Dec-2001: 2.2c1 [Released]
14-Nov-2001: 2.2b2 [Released]
19-Oct-2001: 2.2b1 [Released]
28-Sep-2001: 2.2a4 [Released]
@ -38,40 +37,43 @@ Release Schedule
Release Manager
Barry Warsaw will take over as the release manager. Guido and
Barry will release 2.2a2 together, after that Barry will be
responsible for releases.
Barry Warsaw was the Python 2.2 release manager.
Release Mechanics
We'd like to experiment with a new mechanism for releases: a week
before every alpha, beta or other release, we'll fork off a branch
which will become the release; changes to the branch will have to
be approved before they can be checked in. This is how some other
large projects (e.g. Mozilla) work, and we hope it will help
reduce the number of bugs introduced in releases at the last
minute.
We experimented with a new mechanism for releases: a week before
every alpha, beta or other release, we forked off a branch which
became the release. Changes to the branch are limited to the
release manager and his designated 'bots. This experiment was
deemed a success and should be observed for future releases. See
PEP 101 for the actual release mechanics[1].
Planned features for 2.2
New features for Python 2.2
The following features are already checked in on the head revision
(for a more detailed account, see Misc/NEWS):
The following new features are introduced in Python 2.2. For a
more detailed account, see Misc/NEWS[2] in the Python
distribution, or Andrew Kuchling's "What's New in Python 2.2"
document[3].
- iterators (PEP 234)
- generators (PEP 255)
- unifying long ints and plain ints (PEP 237)
- division (PEP 238)
- unification of types and classes (PEP 252, PEP 253)
Work on the class/type unification is still ongoing.
The following features are under consideration:
References
- unifying long ints and plain ints (PEP 237)
[1] PEP 101, Doing Python Releases 101
http://www.python.org/peps/pep-0101.html
There needs to be more discussion of each of these before we can
decide.
[2] Misc/NEWS file from CVS
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Misc/NEWS?rev=1.337.2.4&content-type=text/vnd.viewcvs-markup
[3] Andrew Kuchling, What's New in Python 2.2
http://www.amk.ca/python/2.2/
Copyright