iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

A few last modifications based on the 2.2 final release.

This commit is contained in:
Barry Warsaw 2001-12-21 20:47:12 +00:00
parent bd48c56a75
commit fe9765bcc1
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-0101.txt
View File

@ -38,9 +38,11 @@ How to Make A Release
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.
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.
@ -421,6 +423,7 @@ How to Make A Release
___ 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,6 +459,8 @@ How to Make A Release
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!
___ Go back to SF, Admin->Edit/Release Files. Click on "Edit