[Python-checkins] r66730 - peps/trunk/pep-0101.txt
georg.brandl
python-checkins at python.org
Thu Oct 2 15:41:14 CEST 2008
Author: georg.brandl
Date: Thu Oct 2 15:41:14 2008
New Revision: 66730
Log:
Updates for doc process.
Modified:
peps/trunk/pep-0101.txt
Modified: peps/trunk/pep-0101.txt
==============================================================================
--- peps/trunk/pep-0101.txt (original)
+++ peps/trunk/pep-0101.txt Thu Oct 2 15:41:14 2008
@@ -145,7 +145,7 @@
___ 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').
___ Doc/tutorial/stdlib.rst and Doc/tutorial/stdlib2.rst, which have
@@ -221,6 +221,8 @@
python26.chm file. He then copies the file into the Doc
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
target architecture (for Python 2.6, this means x86
and AMD64). He has one checkout tree per target architecture,
@@ -293,6 +295,11 @@
% cd Python-2.6c2
% ls
(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
(Loads of configure output)
% make test
@@ -351,6 +358,10 @@
___ 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.
To do these steps, you must have the permission to edit the website. If you
@@ -402,22 +413,9 @@
___ update `doc/content.ht` to indicate the new current documentation
version, and remove the current version from any 'in development'
- section.
-
- ___ 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
+ section. Update the version in the "What's New" link.
- XXX This does not seem complete. I still don't really understand
- how all the documentation stuff hangs together.
+ ___ Add the new version to `doc/version/content.ht`.
___ Edit download/releases/content.ht to update the version numbers for
this release. There are a bunch of places you need to touch:
More information about the Python-checkins
mailing list