From c25b4d926ede4c1176e477221965750d728a10c7 Mon Sep 17 00:00:00 2001
From: Guido van Rossum <guido@python.org>
Date: Fri, 22 Jun 2001 15:36:31 +0000
Subject: [PATCH] Add some text to the release schedule.

The release dates are picked pretty arbitrary: 3 weeks apart, on
Wednesdays.
---
 pep-0251.txt | 50 +++++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 45 insertions(+), 5 deletions(-)

diff --git a/pep-0251.txt b/pep-0251.txt
index b8c590619..63041df73 100644
--- a/pep-0251.txt
+++ b/pep-0251.txt
@@ -1,7 +1,7 @@
 PEP: 251
 Title: Python 2.2 Release Schedule
 Version: $Revision$
-Author: Barry Warsaw <barry@digicool.com>
+Author: Guido van Rossum
 Status: Incomplete
 Type: Informational
 Created: 17-Apr-2001
@@ -15,15 +15,55 @@ Abstract
     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.
+
 
 Release Schedule
 
-    Python 2.2 is in the very early planning stages, and Guido
-    expressed a desire to release Python 2.2 in October of 2001.
+    Tentative future release dates (compare pep-0226) 
 
-    Tentative future release dates
+    17-Oct-2001: 2.2 (final release)
+    10-Oct-2001: 2.2c1 (release candidate)
+    19-Sep-2001: 2.2b2
+    29-Aug-2001: 2.2b1
+     8-Aug-2001: 2.2a2
+    18-Jul-2001: 2.2a1
 
-    October-2001: 2.2 final release
+
+Release Mechanics
+
+    I'd like to experiment with a new mechanism for releases: a week
+    before every alpha, beta or other release, I'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 I hope it will help reduce
+    the number of bugs introduced in releases at the last minute.
+
+
+Planned features for 2.2
+
+    The following features are already checked in on the head revision
+    (for a more detailed account, see Misc/NEWS):
+
+    - iterators (pep-0234)
+
+    The following features are scheduled to go in; work is still
+    ongoing in defining the exact appearance of the features:
+
+    - generators (pep-0255)
+    - unification of types and classes (pep-0252, pep-0253, pep-0254)
+
+    The following features are under consideration:
+
+    - a standard set API (implemented in Python for now) (pep-0218)
+    - a 'directive' statement (pep-0244)
+    - unifying long ints and plain ints (pep-0237)
+
+    There needs to be more discussion of each of these before we can
+    decide.
 
 
 Copyright