Updated release schedule. Reworded various stuff for parallelsim and

conformance to reality.

pep-0283.txt

@@ -22,23 +22,21 @@ Abstract
     release does not count).  Release candidates will be spaced at
     least one week apart (excepting again blunder corrections).
 
-    The schedule so far has had longer gaps than planned:
-
-      alpha 1  --  December 31, 2002
-      alpha 2  --  February 19, 2003
-      beta 1   --  April 25, 2003
-      beta 2   --  June 29, 2003
+      alpha 1      --  31 Dec 2002
+      alpha 2      --  19 Feb 2003
+      beta 1       --  25 April 2003
+      beta 2       --  29 Jun 2003
+      candidate 1  --  18 Jul 2003
 
     Here is the schedule for the remaining releases:
 
-      July 17, 2003 -- rc 1
-      July 24, 2003 -- rc 2 if necessary, otherwise final
-      July 31, 2003 -- final (if rc 2)
+      candidate 2  --  24 Jul 2003
+      final        --  31 Jul 2003
 
 
 Release Manager
 
-    Barry Warsaw, Jeremy Hylton
+    Barry Warsaw, Jeremy Hylton, Tim Peters
 
 
 Completed features for 2.3
@@ -90,7 +88,7 @@ Completed features for 2.3
       few things use this at this time.
 
     - Warn when an extension type's tp_compare returns anything except
-      -1, 0 or 1.  http://www.python.org/sf/472523 
+      -1, 0 or 1.  http://www.python.org/sf/472523
 
     - Warn for assignment to None (in various forms).
 
@@ -154,23 +152,14 @@ Completed features for 2.3
       bits, truncating without range checking.  (SF 595026; Thomas
       Heller did this work.)
 
-    - A new version of IDLE was imported from the IDLEfork project 
+    - A new version of IDLE was imported from the IDLEfork project
       (http://idlefork.sf.net).  The code now lives in the idlelib
       package in the standard library and the idle script is installed
       by setup.py.
 
 Planned features for 2.3
 
-    Here are a few PEPs and other ideas under consideration, with
-    comments in "parade of the PEPs" style.  Not all of these will be
-    part of the final 2.3 release; we'll update the list as decisions
-    crystallize.
-
-    This is pretty much an unordered laundry list.  Please send
-    feedback to python-dev@python.org; I hope to maintain this for the
-    life of the 2.3 development process.
-
-    - The import lock could use some redesign.  (SF 683658.)
+    Too late for anything more to get done here.
 
 
 Ongoing tasks
@@ -209,10 +198,15 @@ Open issues
     before the final release (and preferably before the first beta
     release).  For example:
 
-    - TBD
+    - As of release candidate 1, a raft of mysterious problems
+      cropped up seemingly unique to Cygwin.  If these are really due
+      to the Python core (too soon to guess), it could dely the final
+      release arbitrarily long.
 
 
-Features unlikely to make it into Python 2.3
+Features that did not make it into Python 2.3
+
+    - The import lock could use some redesign.  (SF 683658.)
 
     - Set API issues; is the sets module perfect?