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

More Guido feedback

This commit is contained in:
Barry Warsaw 2001-10-25 15:41:29 +00:00
parent 6f015e9b60
commit 5bcb5cfe0a
1 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
pep-0101.txt
View File

@ -103,10 +103,20 @@ How to Make A Release
to change the PY_VERSION macro, and one or several of the
version subpart macros just above PY_VERSION, as appropriate.
___ For the next approximately 20 hours or so, selectively merge
stuff from trunk into branch. For each change you see on the
trunk (i.e. via the python-checkins mailing list), you need to
decide whether the change should also be applied to the branch.
___ For the next few hours, selectively merge stuff from trunk into
branch. For each change you see on the trunk (i.e. via the
python-checkins mailing list), you need to decide whether the
change should also be applied to the branch.
There is a tension here. Announcing the branch often jogs
people's natural tendency to procrastinate so some very useful
patches end up getting checked in at the last moment. But the
Windows and Docs releases tend to be built many hours before the
source release, and changes to the branch can force a lot of
wasted effort to rebuild them. The best advice is to be
judicious and to consult Fred and Tim before adding anything
big. You really want to avoid skew between the various platform
releases.
Note that committers of changes to the trunk SHOULD include in
the checkin message, a note indicating the suitability of their
@ -122,7 +132,9 @@ How to Make A Release
is to update the Misc/NEWS file. Tim will need this in order to
do the Windows release and he likes to stay up late. This step
can be pretty tedious, so it's best to get to it immediately
after making the branch.
after making the branch, or even before you've made the branch.
The sooner the better (but again, watch for new checkins up
until the release is made!)
Add high level items new to this release. E.g. if we're
releasing 2.2a3, there must be a section at the top of the file