[Python-checkins] CVS: python/nondist/peps pep-0226.txt,1.4,1.5

Jeremy Hylton jhylton@users.sourceforge.net
Fri, 09 Feb 2001 16:19:22 -0800


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

Modified Files:
	pep-0226.txt 
Log Message:
Update release schedule to reflect planned beta and final release.

Begin list of open issues that must be resolved before beta.



Index: pep-0226.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0226.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** pep-0226.txt	2001/01/05 15:10:42	1.4
--- pep-0226.txt	2001/02/10 00:19:20	1.5
***************
*** 18,32 ****
  
  
! Tentative Release Schedule
  
      16-Oct-2000: Python 2.0 final release
  
!     These dates represent goals, not commitments.
  
!     16-Dec-2000: 2.1 PEPs ready for review
!     19-Jan-2001: First 2.1 alpha release
!     23-Feb-2001: First 2.1 beta release
!     01-Apr-2001: 2.1 final release
  
  
  Guidelines for making changes for Python 2.1
--- 18,47 ----
  
  
! Release Schedule
  
+     Tentative future release dates
+ 
+     01-Mar-2001: First 2.1 beta release
+     XX-Mar-2001: Second beta as needed
+     13-Apr-2001: 2.1 final release
+ 
+     Past release dates:
+ 
+     01-Feb-2001: Python 2.1 alpha 2 release
+     22-Jan-2001: Python 2.1 alpha 1 release
      16-Oct-2000: Python 2.0 final release
+ 
+ Open issues for Python 2.0 beta 1
+ 
+     Include Vladimir Marangozov's memory allocator as an optional
+     feature.  It would normally be disabled, but could be enable at
+     configure time.
  
!     Fix the compiler to raise SyntaxErrors with full tracebacks.
  
!     Resolve import issues on case-insensitive, case-preserving file
!     systems. 
  
+     Add a default unit testing framework to the standard library.
  
  Guidelines for making changes for Python 2.1
***************
*** 54,64 ****
      Before the final release, we will have six weeks of beta testing
      and a release candidate or two.
- 
- 
- Bug fix releases before 2.1
- 
-     We may have to issue Python 2.0.1 for critical bug fixes.  If we
-     need to issue a bug fix release, we will use a CVS branch. 
- 
  
  General guidelines for submitting patches and making changes
--- 69,72 ----