On Jun 26, 2009, at 8:49 AM, benjamin.peterson wrote: > Author: benjamin.peterson > Date: Fri Jun 26 14:48:55 2009 > New Revision: 73569 > > Log: > update release candidate shorthand > > Modified: > peps/trunk/pep-0101.txt > > Modified: peps/trunk/pep-0101.txt > = > = > = > = > = > = > = > = > ====================================================================== > --- peps/trunk/pep-0101.txt (original) > +++ peps/trunk/pep-0101.txt Fri Jun 26 14:48:55 2009 > @@ -66,7 +66,7 @@ > > 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.6a3 for Python > 2.6 alpha > - 3, where "a" == alpha, "b" == beta, "c" == release candidate. > + 3, where "a" == alpha, "b" == beta, "rc" == release candidate. > > Final releases are named "releaseXY". The branch tag is > "releaseXY-maint" > because this will point to the long lived maintenance branch. > The fork I'm sure this has been discussed but I missed it. Why was this change made? If nothing else, it breaks many years of tradition. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 832 bytes Desc: This is a digitally signed message part URL: <http://mail.python.org/pipermail/python-dev/attachments/20090626/65737574/attachment.pgp>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4