From 0af7db79f3e1a2b25e44f04d53ec67400ecdd005 Mon Sep 17 00:00:00 2001 From: David Goodger Date: Sat, 13 Aug 2005 12:37:53 +0000 Subject: [PATCH] changed PEP 6 type to Process --- pep-0000.txt | 4 ++-- pep-0006.txt | 13 ++++++++++--- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/pep-0000.txt b/pep-0000.txt index 0f26361ef..749ae0a11 100644 --- a/pep-0000.txt +++ b/pep-0000.txt @@ -35,7 +35,7 @@ Index by Category 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 @@ Numerical Index 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 diff --git a/pep-0006.txt b/pep-0006.txt index a2762d746..16e083f85 100644 --- a/pep-0006.txt +++ b/pep-0006.txt @@ -3,7 +3,7 @@ Title: Bug Fix Releases Version: $Revision$ Author: aahz@pobox.com (Aahz), anthony@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 @@ Prohibitions 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 @@ Not-Quite-Prohibitions 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 @@ Applicability of Prohibitions 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 @@ Helping the Bug Fix Releases Happen 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 @@ Version Numbers 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 @@ Procedure 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 @@ History 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