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

rearrange

This commit is contained in:
Benjamin Peterson 2009-06-26 12:54:46 +00:00
parent ca9ed7bb15
commit 47504f6cf1
1 changed files with 45 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

91
pep-0101.txt
View File

@ -127,52 +127,6 @@ How to Make A Release
use your judgement, taking into account whether you are making an alpha,
beta, or final release.
___ If this is a final major release, branch the tree for X.Y
When making a major release (e.g., for 2.6), you must create the
long-lived maintenance branch. To create a _branch_ (e.g.,
release26-maint), do the following:
.../sandbox/release/release.py --branch X.Y
___ If you just made the release branch, check out a clean version
into a new directory. You'll be doing the release from this new
branch.
% svn co \
svn+ssh://pythondev@svn.python.org/python/branches/release26-maint
___ Set the original trunk up to be the next release.
% .../sandbox/release/release.py --bump 2.7a0
___ Edit all version references in the README
___ Move any historical "what's new" entries from Misc/NEWS to
Misc/HISTORY.
___ The LICENSE file. Add the pending version to the list of
releases, and be sure to check the release dates.
___ There's a copy of the license in Doc/license.rst
___ Doc/tutorial/interpreter.rst (2 references to '[Pp]ython26', one
to 'Python 2.6').
___ Doc/tutorial/stdlib.rst and Doc/tutorial/stdlib2.rst, which have
each one reference to '[Pp]ython26'.
___ Update the version number in configure.in and re-run autoconf.
___ Update the version numbers for the Windows builds in PC/ and
PCbuild/, which have references to python26.
% find PC/ PCbuild/ \( -type f -and -not -wholename '*/.svn/*' \) | xargs sed -i 's/python26/python27/g'
% svn mv PC/os2emx/python26.def PC/os2emx/python27.def
___ cd release26-maint # cd into the branch directory.
___ Regenerate Lib/pydoc-topics.py
cd to the Doc directory and type ``make pydoc-topics``. Then copy
@ -219,6 +173,51 @@ How to Make A Release
alpha or beta releases. Note that Andrew Kuchling often takes care of
this.
___ If this is a final major release, branch the tree for X.Y
When making a major release (e.g., for 2.6), you must create the
long-lived maintenance branch. To create a _branch_ (e.g.,
release26-maint), do the following:
.../sandbox/release/release.py --branch X.Y
___ If you just made the release branch, check out a clean version
into a new directory. You'll be doing the release from this new
branch.
% svn co \
svn+ssh://pythondev@svn.python.org/python/branches/release26-maint
___ Set the original trunk up to be the next release.
% .../sandbox/release/release.py --bump 2.7a0
___ Edit all version references in the README
___ Move any historical "what's new" entries from Misc/NEWS to
Misc/HISTORY.
___ The LICENSE file. Add the pending version to the list of
releases, and be sure to check the release dates.
___ There's a copy of the license in Doc/license.rst
___ Doc/tutorial/interpreter.rst (2 references to '[Pp]ython26', one
to 'Python 2.6').
___ Doc/tutorial/stdlib.rst and Doc/tutorial/stdlib2.rst, which have
each one reference to '[Pp]ython26'.
___ Update the version number in configure.in and re-run autoconf.
___ Update the version numbers for the Windows builds in PC/ and
PCbuild/, which have references to python26.
% find PC/ PCbuild/ \( -type f -and -not -wholename '*/.svn/*' \) | xargs sed -i 's/python26/python27/g'
% svn mv PC/os2emx/python26.def PC/os2emx/python27.def
___ cd release26-maint # cd into the branch directory.
___ Tag the release for X.YaZ
.../sandbox/release/release.py --tag X.YaZ