Add PEP 392, Python 3.2 Release Schedule.

pep-0392.txt

@@ -0,0 +1,87 @@
+PEP: 375
+Title: Python 3.2 Release Schedule
+Version: $Revision $
+Last-Modified: $Date $
+Author: Georg Brandl <georg@python.org>
+Status: Active
+Type: Informational
+Content-Type: text/x-rst
+Created: 30-Dec-2009
+Python-Version: 3.2
+
+
+Abstract
+========
+
+This document describes the development and release schedule for
+Python 3.2.  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.
+
+
+Release Manager and Crew
+========================
+
+======================= ==================
+Position                Name
+======================= ==================
+3.2 Release Manager     Georg Brandl
+Windows installers      Martin v. Loewis
+Mac installers          Ronald Oussoren
+======================= ==================
+
+
+Release Schedule
+================
+
+The current schedule is:
+
+- 3.2 alpha 1: June 26, 2010
+- 3.2 alpha 2: July 24, 2010
+- 3.2 alpha 3: August 21, 2010
+- 3.2 beta 1: September 18, 2010
+
+(No new features beyond this point.)
+
+- 3.2 beta 2: October 16, 2010
+- 3.2 candidate 1: November 13, 2010
+- 3.2 candidate 2: November 27, 2010
+- 3.2 final: December 11, 2010
+
+Every release day listed here is a Saturday; the actual availability
+of the release for download on python.org will depend on the schedules
+of the crew.
+
+
+Features for 3.2
+================
+
+Note that PEP 3003 [#pep3003]_ is in effect: no changes to language
+syntax and no additions to the builtins may be made.
+
+No large-scale changes have been recorded yet.
+
+
+References
+==========
+
+.. [#pep3003]
+   http://www.python.org/dev/peps/pep-3003/
+
+
+
+Copyright
+=========
+
+This document has been placed in the public domain.
+
+
+
+..
+  Local Variables:
+  mode: indented-text
+  indent-tabs-mode: nil
+  sentence-end-double-space: t
+  fill-column: 70
+  coding: utf-8
+  End:

pep-3003.txt

@@ -129,11 +129,11 @@ Allowed to Change
 Retroactive
 ===========
 
-It is important to note that the moratorium covers all changes since the
+It is important to note that the moratorium covers all changes since the release
-release of Python 3.1. This rule is intended to avoid features being rushed or
+of Python 3.1. This rule is intended to avoid features being rushed or smuggled
-smuggled into the CPython source tree while the moratorium is being discussed.
+into the CPython source tree while the moratorium is being discussed.  A review
-A review of the NEWS file for the py3k development branch showed no
+of the NEWS file for the py3k development branch showed no commits would need to
-commits would need to be rolled back in order to meet this goal.
+be rolled back in order to meet this goal.
 
 
 Extensions