Update documentation-related steps.

pep-0101.txt

@@ -295,7 +295,8 @@ How to Make A Release
 
       .../sandbox/release/release.py --export X.YaZ
 
-      This will leave all the relevant files in a subdirectory called 'dist'.
+      This will leave all the relevant files in a subdirectory called 'dist',
+      and the built docs in 'dist/docs'.
 
   ___ scp the files to your home directory on dinsdale.python.org.
 
@@ -377,15 +378,21 @@ How to Make A Release
 
       ___ md5sum the files and make sure they got uploaded intact.
 
-      ___ If this is a final release: Move the built docs to
+      ___ If this is a final release: Move the doc zips and tarballs to
           /data/ftp.python.org/pub/python/doc/X.Y[.Z], and adapt the
           "current" symlink in that directory.
 
       ___ If this is a final release, also unpack the HTML docs to
-          /data/ftp.python.org/pub/www.python.org/doc/X.Y[.Z].
+          /data/ftp.python.org/pub/docs.python.org/release/X.Y[.Z].
 
       ___ Let the DE check if the docs are built and work all right.
 
+      ___ If this is a major release: Tell the DE to adapt redirects for
+          docs.python.org/X.Y in the Apache config for docs.python.org, update
+          the script Doc/tools/dailybuild.py to point to the right
+          stable/development branches, and to install it and make the initial
+          checkout.
+
   Now it's time to twiddle the web site.
 
   To do these steps, you must have the permission to edit the website.  If you
@@ -452,6 +459,8 @@ How to Make A Release
 
       ___ cd to download/releases/X.Y.Z
       ___ Edit the version numbers in content.ht
+      ___ Comment out the link to the documentation if this is not a final,
+          remove the comment if it is.
       ___ Copy the new .asc files into place
       ___ Update the md5 checksums