[Python-checkins] CVS: python/nondist/peps pep-0101.txt,1.18,1.19

2001年12月21日 12:47:14 -0800

Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv25725
Modified Files:
	pep-0101.txt 
Log Message:
A few last modifications based on the 2.2 final release.
Index: pep-0101.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0101.txt,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** pep-0101.txt	2001年12月15日 04:00:17	1.18
--- pep-0101.txt	2001年12月21日 20:47:12	1.19
***************
*** 39,45 ****
 We use the following conventions in the examples below. Where a
 release number is given, it is of the form X.YaZ, e.g. 2.1a3 for
! Python 2.1 alpha 3, where "a" == alpha, "b" == beta, "c" ==
! release candidate, and "f" == final. If a micro release number is
! used, then we'll say X.Y.MaZ.

 ___ At noon the day before the release, create a branch for X.YaZ.
--- 39,47 ----
 We use the following conventions in the examples below. Where a
 release number is given, it is of the form X.YaZ, e.g. 2.1a3 for
! Python 2.1 alpha 3, where "a" == alpha, "b" == beta, "rc" ==
! release candidate. Final releases are named "releaseXY" so the
! branch tag is "releaseXY-branch" and the fork tag on the trunk is
! "releaseXY-fork". If a micro release number is used, then we'll
! say X.Y.MaZ.

 ___ At noon the day before the release, create a branch for X.YaZ.
***************
*** 422,425 ****
--- 424,428 ----
 ___ md5sum the files and make sure they got uploaded intact.

+ 
 ___ Update the X.Y/bugs.ht file if necessary. It is best to get
 BDFL input for this step.
***************
*** 456,459 ****
--- 459,464 ----
 www.python.org and the fact that you're happy with the release)
 and click the SUBMIT button.
+ 
+ Feel free to remove any old news items.

 Now it's time to do some cleanup. These steps are very important!