Update schedule

Add item for accessing new AST from Python code
Remove ongoing tasks section

pep-0356.txt

@@ -19,8 +19,7 @@ Abstract
     beta release.  Bugs may be fixed until the final release.
 
     There will be at least two alpha releases, two beta releases, and
-    one release candidate.  The release date is planned 31 October 2006.
-    (GvR: perhaps one or two months earlier?)
+    one release candidate.  The release date is planned 30 September 2006.
 
 
 Release Manager
@@ -34,14 +33,15 @@ Release Manager
 
 Release Schedule
 
-    (GvR: perhaps one or even two months earlier?  Perhaps three alphas?)
+    (GvR: perhaps one month earlier?  If change, update abstract)
 
-    alpha 1: June 2006 [planned]
-    alpha 2: July 2006 [planned]
-    beta 1:  August 2006 [planned]
-    beta 2:  September 2006 [planned]
-    rc 1:    October 2006 [planned]
-    final:   October 2006 [planned]
+    alpha 1: May 6, 2006 [planned]
+    alpha 2: June 3, 2006 [planned]
+    alpha 3: July 1, 2006 [planned]
+    beta 1:  July 29, 2006 [planned]
+    beta 2:  August 26, 2006 [planned]
+    rc 1:    September 16, 2006 [planned]
+    final:   September 30, 2006 [planned]
 
 
 Completed features for 2.5
@@ -82,45 +82,15 @@ Planned features for 2.5
     PEP 353: Using ssize_t as the index type
     MvL expects this to be complete in March.
 
+    Access to C AST from Python
     (GvR: I have a bunch more that could/would/should be added.)
 
+
 Deferred until 2.6:
 
     - None
 
 
-Ongoing tasks
-
-    (GvR: do we need all these items?  This seems to be just filler.)
-
-    The following are ongoing TO-DO items which we should attempt to
-    work on without hoping for completion by any particular date.
-
-    - Documentation: complete the distribution and installation
-      manuals.
-
-    - Documentation: complete the documentation for new-style
-      classes.
-
-    - Look over the Demos/ directory and update where required (Andrew
-      Kuchling has done a lot of this)
-
-    - New tests.
-
-    - Fix doc bugs on SF.
-
-    - Remove use of deprecated features in the core.
-
-    - Document deprecated features appropriately and update PEP 3000.
-
-    - Mark deprecated C APIs with Py_DEPRECATED.
-
-    - Deprecate modules which are unmaintained, or perhaps make a new
-      category for modules 'Unmaintained'
-
-    - In general, lots of cleanup so it is easier to move forward.
-
-
 Open issues
 
     This PEP needs to be updated and release managers confirmed.