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

updates based on 3.0 final release

This commit is contained in:
Barry Warsaw 2008-12-03 18:42:03 +00:00
parent 2ec984bd6b
commit 263c53b18b
1 changed files with 40 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

76
pep-0101.txt
View File

@ -122,10 +122,49 @@ 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
___ cd release26-maint # cd into the branch directory.
___ 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.
___ Regenerate Lib/pydoc-topics.py
cd to the Doc directory and type ``make pydoc-topics``. Then copy
``build/pydoc-topics/pydoc-topics.py`` to ``../Lib/pydoc-topics.py``.
``build/pydoc-topics/pydoc-topics.py`` to ``../Lib/pydoc_topics.py``.
___ Bump version numbers via the release script.
@ -141,20 +180,6 @@ How to Make A Release
content of this file. You should only need to review the text for
sanity, and update the release date with today's date.
If the minor (middle) digit of the version number changes, you will be
prompted to update some additional files:
___ 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'.
___ Check the years on the copyright notice. If the last release
was some time last year, add the current year to the copyright
notice in several places:
@ -172,9 +197,6 @@ How to Make A Release
contains what purports to be an HTML-ized copy of the LICENSE
file from the distribution. BROKEN
___ For major releases (e.g. 2.6 final), move any historical "what's
new" entries from Misc/NEWS to Misc/HISTORY.
___ Check with the IDLE maintainer to be sure that
Lib/idlelib/NEWS.txt has been similarly updated.
@ -193,24 +215,6 @@ How to Make A Release
For a final release, the RM may block at this point waiting for
confirmation from the Experts.
___ If this is a final major release, branch the tree for X.YaZ
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 a lot of work in this
directory and you want to keep it straight from your trunk working
directory. E.g.
% svn co \
svn+ssh://pythondev@svn.python.org/python/branches/release26-maint
___ cd release26-maint # cd into the branch directory.
___ XXX The WE builds the Windows helpfile, using (in Doc/) either
$ make htmlhelp (on Unix)