[Python-checkins] CVS: python/nondist/peps pep-0102.txt,1.2,1.3

2002年1月10日 08:10:21 -0800

Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv1018
Modified Files:
	pep-0102.txt 
Log Message:
Some relatively minor, er, micro changes. Python 2.1.2 is technically
a micro release of the Python 2.1 branch.
Shortened the title.
Index: pep-0102.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0102.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** pep-0102.txt	2002年01月10日 15:48:26	1.2
--- pep-0102.txt	2002年01月10日 16:10:18	1.3
***************
*** 1,10 ****
 PEP: 102
! Title: Doing Python Releases 102 - The Minor Releases
 Version: $Revision$
 Last-Modified: $Date$
! Author: barry@zope.com (Barry A. Warsaw), guido@python.org (Guido van Rossum), anthony@interlink.com.au (Anthony Baxter)
 Status: Active
 Type: Informational
! Created: 22-Aug-2001 (edited down on 9-Jan-2002 to become pep-0102)
 Post-History:

--- 1,12 ----
 PEP: 102
! Title: Doing Python Micro Releases
 Version: $Revision$
 Last-Modified: $Date$
! Author: anthony@interlink.com.au (Anthony Baxter)
! barry@zope.com (Barry A. Warsaw)
! guido@python.org (Guido van Rossum)
 Status: Active
 Type: Informational
! Created: 22-Aug-2001 (edited down on 9-Jan-2002 to become PEP 102)
 Post-History:

***************
*** 17,23 ****
 Guido himself. But several recent releases have been performed by
 other folks, so this PEP attempts to collect, in one place, all
! the steps needed to make a Python bugfix release. The major Python
! release process is covered in PEP 101 - this PEP is just 101, trimmed
! down to only include the bits that are relevant for minor releases.

 It is organized as a recipe and you can actually print this out and 
--- 19,27 ----
 Guido himself. But several recent releases have been performed by
 other folks, so this PEP attempts to collect, in one place, all
! the steps needed to make a Python bugfix release.
! 
! The major Python release process is covered in PEP 101 - this PEP
! is just PEP 101, trimmed down to only include the bits that are
! relevant for micro releases, a.k.a. patch, or bug fix releases.

 It is organized as a recipe and you can actually print this out and 
***************
*** 41,50 ****

 We use the following conventions in the examples below. Where a
! release number is given, it is of the form X.Y.MaA, e.g. 2.1.2rc1 for
! Python 2.1.2 release candidate 1, where "a" == alpha, "b" == beta, 
! "rc" == release candidate. Final releases are tagged with "releaseXYZ" 
! in CVS. The minor releases are made from the maintenance branch of the
! major release, e.g. Python 2.1.2 is made from the release21-maint 
! branch.

 ___ Send an email to python-dev@python.org indicating the release is 
--- 45,54 ----

 We use the following conventions in the examples below. Where a
! release number is given, it is of the form X.Y.MaA, e.g. 2.1.2c1
! for Python 2.1.2 release candidate 1, where "a" == alpha, "b" ==
! beta, "c" == release candidate. Final releases are tagged with
! "releaseXYZ" in CVS. The micro releases are made from the
! maintenance branch of the major release, e.g. Python 2.1.2 is made
! from the release21-maint branch.

 ___ Send an email to python-dev@python.org indicating the release is 
***************
*** 90,94 ****
 about changes on the Mac.

! This command should help you:

 % cvs log -rr22a1: | python Tools/scripts/logmerge.py > /tmp/news.txt
--- 94,98 ----
 about changes on the Mac.

! This command should help you (but substitute the correct -r tag!):

 % cvs log -rr22a1: | python Tools/scripts/logmerge.py > /tmp/news.txt