Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1:/tmp/cvs-serv23028 Modified Files: pep-0101.txt Log Message: Update some of the information about documentation build procedures. Much of it was outdated. I still need to document *how* some of the steps are carried out. Index: pep-0101.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0101.txt,v retrieving revision 1.39 retrieving revision 1.40 diff -C2 -d -r1.39 -r1.40 *** pep-0101.txt 22 Sep 2003 01:11:35 -0000 1.39 --- pep-0101.txt 30 Sep 2003 03:46:52 -0000 1.40 *************** *** 167,173 **** proclaiming its identity. - ___ There's also a mention of the version in - Doc/texinputs/boilerplate.tex; Fred usually takes care of that. - ___ If the major (first) or minor (middle) digit of the version number changes, also update the LICENSE file. --- 167,170 ---- *************** *** 206,226 **** that Andrew often takes care of this. ! ___ By now, Fred has created the HTML for the documentation and ! pushed the appropriate files out to www.python.org. Tim needs ! this to build the Windows installer, but the RM doesn't need ! this stuff to build the source distribution. ! Fred tells Tim Peters and Sean Reifschneider where the ! documentation 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, and to Hernan ! M. Foffani for conversion to HTML Help. 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. ___ Tim performs his Windows magic, generating an installer --- 203,221 ---- that Andrew often takes care of this. ! ___ At this point, Fred will create the formatted versions of the ! documentation and push the appropriate files out to their FTP ! locations on www.python.org. The HTML format is used to build ! the HTML Help format for the Windows installer, but the RM ! doesn't need this to build the source distribution. The HTML ! Help format will typically be generated by whoever builds the ! Windows installer. ! Once Fred is done, there can be no further checkins on the ! branch in the Doc/ directory -- not even by the RM. Basically, if it's in Doc/, Fred will take care of it. ! ___ Tim Peters grabs the HTML Help format and uses this to build the ! Windows installer. ___ Tim performs his Windows magic, generating an installer *************** *** 255,262 **** working on the trunk. ! You should not see any "M" files, but you may see several "P" ! files. I.e. you better not have any uncommitted changes in your ! working directory, but you may pick up some of Fred's or Tim's ! last minute changes. ___ If you've seen updates to existing files, update the cvs tag: --- 250,257 ---- working on the trunk. ! You should not see any "M" files, but you may see several "P" or ! "U" files. I.e. you better not have any uncommitted changes in ! your working directory, but you may pick up some of Fred's or ! Tim's last minute changes. ___ If you've seen updates to existing files, update the cvs tag: