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

Move instructions for building the HTML Help into PEP 101 from PEP 102; this 

locates all the instructions for building documentation in one of the PEPs;
the other incorporates the instructions by reference.
This commit is contained in:
Fred Drake 2003-09-30 04:49:33 +00:00
parent 69eb8f0f61
commit 4de8d6823c
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-0101.txt
View File

@ -238,8 +238,15 @@ How to Make A Release
website should be added here, or there should be a link to a website should be added here, or there should be a link to a
document in the python.org site management documentation. document in the python.org site management documentation.
XXX Someone who knows how to build the HTML Help format should ___ Thomas grabs the HTML to build the Windows helpfile.
add a description of that process. The HTML files are unpacked into a new src/html directory, and
runs this command to create the project files for MS HTML
Workshop:
% 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.
___ Tim Peters grabs the HTML Help format and uses this to build the ___ Tim Peters grabs the HTML Help format and uses this to build the
Windows installer. Windows installer.

13
pep-0102.txt
View File

@ -137,16 +137,9 @@ How to Make A Release
___ Check your NEWS changes into the maintenance branch. It's easy ___ Check your NEWS changes into the maintenance branch. It's easy
to forget to update the release date in this file! to forget to update the release date in this file!
___ Once the release is underway, Fred Drake needs to create the ___ Once the release process has started, the documentation needs to
HTML from the documentation. He does this and uploads the file be built and posted on python.org according to the instructions
to www.python.org. Then he tells Thomas and Sean Reifschneider in PEP 101.
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,
Fred also sends email to Milan Zamazal for conversion to the GNU
Info format.
Note that Fred is responsible both for merging doc changes from Note that Fred is responsible both for merging doc changes from
the trunk to the branch AND for merging any branch changes from the trunk to the branch AND for merging any branch changes from