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 minor additions based on the last go-round.

This commit is contained in:
Barry Warsaw 2001-12-15 04:00:17 +00:00
parent 458e871365
commit 7f11eaf188
1 changed files with 20 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
pep-0101.txt
View File

@ -149,10 +149,11 @@ How to Make A Release
This command should help you:
% cvs log -rr22a2: | python Tools/scripts/logmerge.py > /tmp/news.txt
% cvs log -rr22a1: | 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.
IOW, you're printing out all the cvs log entries from the
previous release until now. 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.
@ -292,9 +293,12 @@ How to Make A Release
include the announcement.
___ In the python.org web site CVS tree, cd to the X.Y
subdirectory, and copy index.ht to new-index.ht
subdirectory, and copy index.ht to new-index.ht. Be sure to
do a "cvs update" first!
% cd .../pydotorg/2.2
% cd .../pydotorg
% cvs -q up -P -d
% cd 2.2
% cp index.ht new-index.ht
___ Edit the file for content: usually you can globally replace
@ -415,6 +419,8 @@ How to Make A Release
sure they are world readable. They should also be group
writable, and group-owned by webmaster.
___ 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.
@ -475,9 +481,15 @@ How to Make A Release
___ Edit diffcmd.sh to get rid of files that you know don't have
important changes. You're looking for files that have updates
in the branch that haven't made it to the trunk. If you've
been diligent about merging changes from the trunk into the
branch, there shouldn't be many of these files.
in the branch that haven't made it to the trunk.
Generally you can ignore any changes to the Doc or Mac
subdirectories, or any changes to Windows related files. The
sub-RMs for those parts will take care of any necessary merges
from the branch to the trunk.
If you've been diligent about merging changes from the trunk
into the branch, there shouldn't be many of these files.
___ Edit /tmp/diffcmd.sh, changing all the -r's into -u's. Run
the /tmp/diffcmd.sh command like so: