Just a few more minor updates based on the 2.2b2 release.
This commit is contained in:
parent
9b34eda376
commit
78aca90a70
18
pep-0101.txt
18
pep-0101.txt
|
@ -147,6 +147,15 @@ How to Make A Release
|
||||||
verify with Tim Peters about changes on Windows, and Jack Jansen
|
verify with Tim Peters about changes on Windows, and Jack Jansen
|
||||||
about changes on the Mac.
|
about changes on the Mac.
|
||||||
|
|
||||||
|
This command should help you:
|
||||||
|
|
||||||
|
% cvs log -rr22a2: | python Tools/scripts/logmerge.py > /tmp/news.txt
|
||||||
|
|
||||||
|
You can then troll through the news.txt file looking for
|
||||||
|
interesting things to add to NEWS.
|
||||||
|
|
||||||
|
___ Check your NEWS changes into the branch and into the trunk.
|
||||||
|
|
||||||
___ Once the branch is frozen, Fred Drake needs to create the HTML
|
___ Once the branch is frozen, Fred Drake needs to create the HTML
|
||||||
from the documentation. He does this and uploads the file to
|
from the documentation. He does this and uploads the file to
|
||||||
www.python.org. Then he tells Tim Peters where this file is.
|
www.python.org. Then he tells Tim Peters where this file is.
|
||||||
|
@ -163,7 +172,8 @@ How to Make A Release
|
||||||
|
|
||||||
___ Tim Peters grabs the HTML and uses this to build the Windows
|
___ Tim Peters grabs the HTML and uses this to build the Windows
|
||||||
installer. Tim then creates a new "release" named X.YaZ on the
|
installer. Tim then creates a new "release" named X.YaZ on the
|
||||||
SourceForge file release manager.
|
SourceForge file release manager. (Although, if you get there
|
||||||
|
first, you should create the new release.)
|
||||||
|
|
||||||
(Diversion: SF's file manager has "packages" and "releases". We
|
(Diversion: SF's file manager has "packages" and "releases". We
|
||||||
use packages to name major upcoming releases, e.g. python-2.2 or
|
use packages to name major upcoming releases, e.g. python-2.2 or
|
||||||
|
@ -452,10 +462,8 @@ How to Make A Release
|
||||||
|
|
||||||
___ Run a diff against your branch by doing this in the common
|
___ Run a diff against your branch by doing this in the common
|
||||||
parent directory containing both python-clean and python-XYaZ:
|
parent directory containing both python-clean and python-XYaZ:
|
||||||
% diff -r python-clean python-22a2 | grep ^diff | grep -v CVS
|
% diff -r python-clean python-22a2 | grep ^diff | grep -v CVS \
|
||||||
|
> /tmp/diffcmd.sh
|
||||||
___ Take the output of this and stick it in a file,
|
|
||||||
e.g. /tmp/diffcmd.sh
|
|
||||||
|
|
||||||
___ Edit diffcmd.sh to get rid of files that you know don't have
|
___ Edit diffcmd.sh to get rid of files that you know don't have
|
||||||
important changes. You're looking for files that have updates
|
important changes. You're looking for files that have updates
|
||||||
|
|
Loading…
Reference in New Issue