[Python-checkins] CVS: python/nondist/peps pep-0251.txt,1.2,1.3

Guido van Rossum gvanrossum@users.sourceforge.net
Mon, 13 Aug 2001 14:03:14 -0700


Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv20670

Modified Files:
	pep-0251.txt 
Log Message:
Make Barry co-author; slip the schedule (including a new a3 release);
tighten list of planned features.


Index: pep-0251.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0251.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** pep-0251.txt	2001/06/22 15:36:31	1.2
--- pep-0251.txt	2001/08/13 21:03:12	1.3
***************
*** 2,6 ****
  Title: Python 2.2 Release Schedule
  Version: $Revision$
! Author: Guido van Rossum
  Status: Incomplete
  Type: Informational
--- 2,6 ----
  Title: Python 2.2 Release Schedule
  Version: $Revision$
! Author: guido@python.org (Guido van Rossum), barry@zope.com (Barry A. Warsaw)
  Status: Incomplete
  Type: Informational
***************
*** 24,45 ****
  Release Schedule
  
!     Tentative future release dates (compare pep-0226) 
  
!     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
  
  
  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.
  
  
--- 24,55 ----
  Release Schedule
  
!     Tentative future release dates.  Note that we've slipped this
!     compared to the schedule posted around the release of 2.2a1.
  
!     19-Dec-2001: 2.2   (final release)
!     12-Dec-2001: 2.2c1 (release candidate)
!     14-Nov-2001: 2.2b2
!     10-Oct-2001: 2.2b1
!     19-Sep-2001: 2.2a3 (new! a third alpha)
!     22-Aug-2001: 2.2a2
      18-Jul-2001: 2.2a1
  
  
+ 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.
+ 
+ 
  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.
  
  
***************
*** 48,65 ****
      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
--- 58,72 ----
      The following features are already checked in on the head revision
      (for a more detailed account, see Misc/NEWS):
  
!     - iterators (PEP 234)
!     - generators (PEP 255)
!     - 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:
  
!     - unifying long ints and plain ints (PEP 237)
  
      There needs to be more discussion of each of these before we can