From bb3f415cdcd9d1c8de882f38b2a724cfa009673c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20v=2E=20L=C3=B6wis?= Date: Sun, 10 Sep 2006 16:56:11 +0000 Subject: [PATCH] Document current Windows release process. --- pep-0101.txt | 39 +++++++++++++++++++++------------------ 1 file changed, 21 insertions(+), 18 deletions(-) diff --git a/pep-0101.txt b/pep-0101.txt index e5c4c8359..b7468a10b 100644 --- a/pep-0101.txt +++ b/pep-0101.txt @@ -339,7 +339,7 @@ How to Make A Release releases. (Is should be fairly easy to figure this out while looking at the file.) - ___ Thomas grabs the HTML to build the Windows helpfile. + ___ Martin grabs the HTML to build the Windows helpfile. The HTML files are unpacked into a new src/html directory, and runs this command to create the project files for MS HTML Workshop: @@ -347,23 +347,30 @@ How to Make A Release % python ..\Doc\tools\prechm.py -v 2.3 python23 HTML Workshop is then fired up on the created python23.hhp file, - finally resulting in an python23.chm file. + finally resulting in an python23.chm file. He then copies the + file into the Doc directories of the build trees (once for + each target architecture). - ___ Tim Peters grabs the HTML Help format and uses this to build the - Windows installer. + ___ Martin then generates Windows installer files for each Windows + target architecture (for Python 2.5, this means x86, Itanium, + and AMD64). He has one checkout tree per target architecture, + and builds the pcbuild.sln project for the appropriate + architecture. He then edits Tools/msi/config.py to update + full_current_version, and runs msi.py with ActivePython 2.3. + For that to work, the following prerequisites must be met: - ___ Tim performs his Windows magic, generating an installer - executable. He uploads this file to SourceForge, and then sends - the RM a notice which includes the location and MD5 checksum of - the Windows executable. + - PC/icons.mak must have been run with nmake. - Note that Tim used to upload the installer to www.python.org, - but has had problems with ssh for a while now. + - The cmd.exe window in which this is run must have Cygwin/bin + in its path (atleast for x86). - 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. + - The cmd.exe window must have MS compiler tools for the target + architecture in its path (VS 2003 for x86, the platform + SDK for Itanium and AMD64). + + Martin checksums the files (*.msi and *.chm), uploads them + to some place in the net, and emails you the location + and md5sums. ___ Sean Reifschneider grabs the HTML and uses this to build the Linux RPMs. Sean performs his Red Hat magic, generating a set @@ -371,10 +378,6 @@ How to Make A Release the RM a notice which includes the location and MD5 checksum of the RPMs. - ___ Download the Windows executable from SourceForge to - creosote.python.org. Tell Tim so he can remove the file from - SourceForge. - ___ Time to build the source tarball. If you created a branch, be sure to cd to your working directory for the branch. E.g. % cd .../python-22a3