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

Nix RPM steps; update timezones.

This commit is contained in:
Barry Warsaw 2008-10-02 18:13:46 +00:00
parent 19b903da5b
commit 48607faa8e
1 changed files with 2 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-0101.txt
View File

@ -36,10 +36,9 @@ How to Make A Release
current experts are: current experts are:
* RM = Release Manager: Barry Warsaw <barry@python.org> (US/Eastern) * RM = Release Manager: Barry Warsaw <barry@python.org> (US/Eastern)
* WE = Windows: Martin von Loewis <martin@v.loewis.de> * WE = Windows: Martin von Loewis <martin@v.loewis.de> (Central Europe)
* ME = Mac: Ronald Oussoren <ronaldoussoren@mac.com> * ME = Mac: Ronald Oussoren <ronaldoussoren@mac.com> (Central Europe)
* IE = Idle Expert: ?? * IE = Idle Expert: ??
* RE = RPM Expert: Sean Reifschneider <jafo@tummy.com>
NOTE: It is highly recommended that the RM contact the Experts the day NOTE: It is highly recommended that the RM contact the Experts the day
before the release. Because the world is round and everyone lives before the release. Because the world is round and everyone lives
@ -247,12 +246,6 @@ How to Make A Release
The WE checksums the files (*.msi and *.chm), uploads them to The WE checksums the files (*.msi and *.chm), uploads them to
some place in the net, and emails you the location and md5sums. some place in the net, and emails you the location and md5sums.
___ XXX Sean Reifschneider grabs the HTML and uses this to build the
Linux RPMs. 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.
___ Time to build the source tarball. If you created a branch, be ___ Time to build the source tarball. If you created a branch, be
sure to cd to your working directory for the branch. E.g. sure to cd to your working directory for the branch. E.g.