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

Updates for doc process.

This commit is contained in:
Georg Brandl 2008-10-02 13:41:14 +00:00
parent 9020d2a184
commit 19b903da5b
1 changed files with 14 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
pep-0101.txt
View File

@ -145,7 +145,7 @@ How to Make A Release
___ There's a copy of the license in Doc/license.rst ___ There's a copy of the license in Doc/license.rst
___ Doc/tutorial/interpreter.rst (3 references to '[Pp]ython26', one ___ Doc/tutorial/interpreter.rst (2 references to '[Pp]ython26', one
to 'Python 2.6'). to 'Python 2.6').
___ Doc/tutorial/stdlib.rst and Doc/tutorial/stdlib2.rst, which have ___ Doc/tutorial/stdlib.rst and Doc/tutorial/stdlib2.rst, which have
@ -221,6 +221,8 @@ How to Make A Release
python26.chm file. He then copies the file into the Doc python26.chm file. He then copies the file into the Doc
directories of the build trees (once for each target architecture). directories of the build trees (once for each target architecture).
XXX The CHM file should also be scp'd to the docs download location.
___ XXX The WE then generates Windows installer files for each Windows ___ XXX The WE then generates Windows installer files for each Windows
target architecture (for Python 2.6, this means x86 target architecture (for Python 2.6, this means x86
and AMD64). He has one checkout tree per target architecture, and AMD64). He has one checkout tree per target architecture,
@ -293,6 +295,11 @@ How to Make A Release
% cd Python-2.6c2 % cd Python-2.6c2
% ls % ls
(Do things look reasonable?) (Do things look reasonable?)
% ls Lib
(Are there stray .pyc files?)
% ls Doc/tools
(Make sure it doesn't contain "docutils", "sphinx", "jinja" or
"pygments" directories.)
% ./configure % ./configure
(Loads of configure output) (Loads of configure output)
% make test % make test
@ -351,6 +358,10 @@ How to Make A Release
___ md5sum the files and make sure they got uploaded intact. ___ md5sum the files and make sure they got uploaded intact.
___ If this is a final release: Move the built docs to
/data/ftp.python.org/pub/python/doc/X.Y[.Z], and adapt the
"current" symlink in that directory.
Now it's time to twiddle the web site. Now it's time to twiddle the web site.
To do these steps, you must have the permission to edit the website. If you To do these steps, you must have the permission to edit the website. If you
@ -402,22 +413,9 @@ How to Make A Release
___ update `doc/content.ht` to indicate the new current documentation ___ update `doc/content.ht` to indicate the new current documentation
version, and remove the current version from any 'in development' version, and remove the current version from any 'in development'
section. section. Update the version in the "What's New" link.
___ add the new version to `doc/version/content.ht` ___ Add the new version to `doc/version/content.ht`.
___ Make the last change to the documentation area on python.org.
The "current" symlink needs to be updated if this release is the
highest-versioned release. Log in to dinsdale.python.org, and
update a symlink in the doc/ tree:
# on dinsdale:
$ cd /data/ftp.python.org/pub/www.python.org/doc/
$ rm current && ln -s $VERSION current
XXX This does not seem complete. I still don't really understand
how all the documentation stuff hangs together.
___ Edit download/releases/content.ht to update the version numbers for ___ Edit download/releases/content.ht to update the version numbers for
this release. There are a bunch of places you need to touch: this release. There are a bunch of places you need to touch: