[Python-checkins] python/nondist/peps pep-0283.txt,1.30,1.31

[gvanrossum@users.sourceforge.net]

Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1:/tmp/cvs-serv10865

Modified Files:
	pep-0283.txt 
Log Message:
Explain feature freeze.
Mention IDLE.


Index: pep-0283.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0283.txt,v
retrieving revision 1.30
retrieving revision 1.31
diff -C2 -d -r1.30 -r1.31
*** pep-0283.txt	19 Feb 2003 19:10:33 -0000	1.30
--- pep-0283.txt	19 Feb 2003 19:36:27 -0000	1.31
***************
*** 13,18 ****
      This document describes the development and release schedule for
      Python 2.3.  The schedule primarily concerns itself with PEP-sized
!     items.  Small features may be added until the first beta release.
!     Bugs may be fixed until the final release.
  
      There will be at least two alpha releases, two beta releases, and
--- 13,18 ----
      This document describes the development and release schedule for
      Python 2.3.  The schedule primarily concerns itself with PEP-sized
!     items.  Small features may be added up to and including the first
!     beta release.  Bugs may be fixed until the final release.
  
      There will be at least two alpha releases, two beta releases, and
***************
*** 23,31 ****
      least one week apart (excepting again blunder corrections).
  
!     Based on the first alpha release, which was made on Dec. 31, 2002,
!     here's a fairly aggressive release schedule that follows the above
      guidelines:
  
!       alpha 2  --  mid February
        beta 1   --  late March
        beta 2   --  late April
--- 23,30 ----
      least one week apart (excepting again blunder corrections).
  
!     Here's a tentative release schedule that follows the above
      guidelines:
  
!       alpha 2  --  February 19, 2003
        beta 1   --  late March
        beta 2   --  late April
***************
*** 150,153 ****
--- 149,155 ----
      feedback to python-dev@python.org; I hope to maintain this for the
      life of the 2.3 development process.
+ 
+     - I plan to integrate the new version of IDLE from the IDLEfork
+       project (http://idlefork.sf.net).
  
      - We need a new PyArg_Parse*() format code that returns an