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

updates from Sean.

This commit is contained in:
Anthony Baxter 2003-09-22 04:25:19 +00:00
parent 758bca047f
commit 5f43f66c42
1 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
pep-0102.txt
View File

@ -2,8 +2,8 @@ PEP: 102
Title: Doing Python Micro Releases
Version: $Revision$
Last-Modified: $Date$
Author: anthony@interlink.com.au (Anthony Baxter)
barry@zope.com (Barry A. Warsaw)
Author: anthony@interlink.com.au (Anthony Baxter),
barry@zope.com (Barry A. Warsaw),
guido@python.org (Guido van Rossum)
Status: Active
Type: Informational
@ -67,6 +67,11 @@ 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.
___ Change the "%define version" line of Misc/RPM/python-2.3.spec to the
same string as PY_VERSION was changed to above. E.g:
%define version 2.3.1
___ If you're changing the version number for Python (e.g. from
Python 2.1.1 to Python 2.1.2), you also need to update the
README file, which has a big banner at the top proclaiming its
@ -118,7 +123,8 @@ How to Make A Release
___ Once the release is underway, Fred Drake needs to create the
HTML 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 and Sean Reifschneider
where this file is.
This may generate some last minute changes on the branch. Once
Fred is done, there can be no further checkins on the branch in
the Doc/ directory -- not even by the RM. For final releases,
@ -131,18 +137,23 @@ How to Make A Release
Basically, if it's in Doc/ Fred will take care of it.
___ Tim Peters grabs the HTML and uses this to build the Windows
installer.
installer, Sean Reifschneider grabs the HTML and uses this to
build the Linux RPMs.
___ Tim performs his Windows magic, generating an installer
executable. He uploads this file to python.org. He then sends
the RM a notice which includes the location and MD5 checksum of
the Windows executable.
the Windows executable.
Note that Tim's creation of the Windows executable may generate
a few more commits on the branch. Tim will be responsible for
merging Windows-specific changes from trunk to branch, and from
branch to trunk.
___ Sean performs his Red Hat magic, generating a set of RPMs. He
uploads these files to python.org. He then sends the RM a notice
which includes the location and MD5 checksum of the RPMs.
___ It's Build Time!
Now, you're ready to build the source tarball. First cd to your