[Python-checkins] python/nondist/peps pep-0006.txt, 1.11, 1.12 pep-0000.txt, 1.340, 1.341

goodger@users.sourceforge.net goodger at users.sourceforge.net
Sat Aug 13 14:38:03 CEST 2005


Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25234

Modified Files:
	pep-0006.txt pep-0000.txt 
Log Message:
changed PEP 6 type to Process

Index: pep-0006.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0006.txt,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- pep-0006.txt	19 Aug 2004 07:06:12 -0000	1.11
+++ pep-0006.txt	13 Aug 2005 12:37:53 -0000	1.12
@@ -3,7 +3,7 @@
 Version: $Revision$
 Author: aahz at pobox.com (Aahz), anthony at interlink.com.au (Anthony Baxter)
 Status: Active
-Type: Informational
+Type: Process
 Created: 15-Mar-2001
 Post-History: 15-Mar-2001 18-Apr-2001 19-Aug-2004
 
@@ -55,6 +55,7 @@
     Breaking any of these prohibitions requires a BDFL proclamation
     (and a prominent warning in the release notes). 
 
+
 Not-Quite-Prohibitions
 
     Where possible, bug fix releases should also:
@@ -69,6 +70,7 @@
        the standard library should not change behavior, or worse yet,
        APIs.
 
+
 Applicability of Prohibitions
 
     The above prohibitions and not-quite-prohibitions apply both
@@ -80,6 +82,7 @@
     the community happy that a bug fix release is a painless and safe
     upgrade.
 
+
 Helping the Bug Fix Releases Happen
 
     Here's a few pointers on helping the bug fix release process along.
@@ -98,6 +101,7 @@
        wait until 48 hours before a bug fix release is due, and then
        start asking for bug fixes to be included.
 
+
 Version Numbers
 
     Starting with Python 2.0, all major releases are required to have
@@ -111,10 +115,11 @@
     the branch is named 'release2x-maint'. For example, the branch for
     the 2.3 maintenance releases is release23-maint
 
+
 Procedure
 
-    The process for managing bugfix releases is modeled in part on the Tcl
-    system [1].
+    The process for managing bugfix releases is modeled in part on the
+    Tcl system [1].
 
     The Patch Czar is the counterpart to the BDFL for bugfix releases.
     However, the BDFL and designated appointees retain veto power over
@@ -151,6 +156,7 @@
     bugfix releases. If, however, someone qualified wishes to continue
     the work to maintain an older release, they should be encouraged.
 
+
 Patch Czar History
 
     Anthony Baxter is the Patch Czar for 2.3.1 through 2.3.4.
@@ -190,6 +196,7 @@
     Anthony Baxter then took this PEP and revised it, based on 
     lessons from the 2.3 release cycle. 
 
+
 References
 
     [1] http://www.tcl.tk/cgi-bin/tct/tip/28.html

Index: pep-0000.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0000.txt,v
retrieving revision 1.340
retrieving revision 1.341
diff -u -d -r1.340 -r1.341
--- pep-0000.txt	13 Aug 2005 01:37:32 -0000	1.340
+++ pep-0000.txt	13 Aug 2005 12:37:53 -0000	1.341
@@ -35,7 +35,7 @@
  I     3  Guidelines for Handling Bug Reports          Hylton
  I     4  Deprecation of Standard Modules              von Loewis
  I     5  Guidelines for Language Evolution            Prescod
- I     6  Bug Fix Releases                             Aahz
+ P     6  Bug Fix Releases                             Aahz
  I     7  Style Guide for C Code                       GvR
  I     8  Style Guide for Python Code                  GvR, Warsaw
  I     9  Sample Plaintext PEP Template                Warsaw
@@ -230,7 +230,7 @@
  I     3  Guidelines for Handling Bug Reports          Hylton
  I     4  Deprecation of Standard Modules              von Loewis
  I     5  Guidelines for Language Evolution            Prescod
- I     6  Bug Fix Releases                             Aahz
+ P     6  Bug Fix Releases                             Aahz
  I     7  Style Guide for C Code                       GvR
  I     8  Style Guide for Python Code                  GvR, Warsaw
  I     9  Sample Plaintext PEP Template                Warsaw



More information about the Python-checkins mailing list