Made a first attempt at updating PEP 101 on how to update the new web site.

Also updated the 3.5 release schedule with final dates for rc2 and rc3.

pep-0101.txt

@@ -35,12 +35,15 @@ Things You'll Need
       which hopefully will be on the "web of trust" with at least one of
       the other release managers.
 
-    * Access to ``dl-files.iad1.psf.io``, the server that hosts download files.
+    * Access to ``dl-files.iad1.psf.io``, the server that hosts download files,
+      and ``docs.iad1.psf.io``, the server that hosts the documentation.
       You'll be uploading files directly here.
 
     * Shell access to ``hg.python.org``, the Python Mercurial host.  You'll
       have to adapt repository configuration there.
 
+    * An administratior account on www.python.org, including an "API key".
+
     * Write access to the PEP repository.
 
       If you're reading this, you probably already have this--the first
@@ -161,7 +164,7 @@ How to Make A Release
       extra effort.
 
   ___ Make sure the current branch of your release clone is the branch you
-      want to release from.
+      want to release from.  (``hg id``)
 
   ___ Check the docs for markup errors.
 
@@ -299,7 +302,7 @@ How to Make A Release
 
   ___ The WE builds the Windows helpfile, using (in Doc/)
 
-      > make.bat htmlhelp   (on Windows)
+      % make.bat htmlhelp   (on Windows)
 
       to create suitable input for HTML Help Workshop in build/htmlhelp. HTML
       Help Workshop is then fired up on the created python33.hhp file, finally
@@ -460,7 +463,8 @@ How to Make A Release
 
   To do these steps, you must have the permission to edit the website.  If you
   don't have that, ask someone on pydotorg@python.org for the proper
-  permissions.  It's insane for you not to have it.
+  permissions.  (Or ask Ewa, who coordinated the effort for the new newbsite
+  with RevSys.)
 
   XXX This is completely out of date for Django based python.org.
 
@@ -470,46 +474,72 @@ How to Make A Release
 
   None of the web site updates are automated by release.py.
 
-  ___ Build the basic site.
-
-      In the top directory, do an `svn update` to get the latest code.  In the
-      build subdirectory, do `make` to build the site.  Do `make serve` to
-      start service the pages on localhost:8005.  Hit that url to see the site
-      as it is right now.  At any time you can re-run `make` to update the
-      local site.  You don't have to restart the server.
-
-      Don't `svn commit` until you're all done!
+  ___ Log in to http://www.python.org/admin .
 
   ___ If this is the first release for this version (even a new patch
-      version), you'll need to create a subdirectory inside download/releases
-      to hold the new version files.  It's probably a good idea to copy an
-      existing recent directory and twiddle the files in there for the new
-      version number.
+      version), you'll need to create a "page" for the version.
+      Find the "Pages" section and click on "Add", then fill in the
+      form.
 
-  ___ Update the version specific pages.
+      Note that the easiest thing is probably to copy fields from
+      an existing Python release "page", editing as you go.
 
-      ___ cd to `download/releases/X.Y.Z`
-      ___ Edit the version numbers in content.ht
-      ___ Update the md5 checksums
+  ___ If this isn't the first release for a version, open the existing
+      "page" for editing and update it to the new release.  Don't save yet!
 
-      ___ Comment out the "This is a preview release" or the "This is a
-          production release" paragraph as appropriate
+  ___ Now create a new "release" for the release.  Currently "Releases" are
+      sorted under "Downloads".
 
-      Note, you don't have to copy any release files into this directory;
-      they only live on dl-files.iad1.psf.io in the ftp directory.
+      Again, the easiest thing is probably to copy fields from
+      an existing Python release "page", editing as you go.
 
-  ___ Edit `download/releases/content.ht` to update the version numbers for
-      this release.  There are a bunch of places you need to touch:
+      The mysterious "Release page" field on the form needs the
+      ID number of the "page" for this version.  You can get that
+      by examining the URL for the "change page" form for this
+      version.  For example, the URL for editing the "page"
+      for Python 3.5 is:
 
-      ___ The subdirectory name as the first element in the Nav rows.
-      ___ Possibly the Releases section, and possibly in the experimental
-          releases section if this is an alpha, beta or release candidate.
+      https://www.python.org/admin/pages/page/1232/
 
-  ___ Update the download page, editing `download/content.ht`.  Pre-releases are
-      added only to the "Testing versions" list.
+      The page's ID number is the last field; here it is 1232.
+
+  ___ Note that by convention, the "Content" on the page and
+      the "Content" on the release are the same, *except* the
+      "page" has a section on where to download the software.
+
+  ___ "Save" the release.
+
+  ___ Populate the release with the downloadable files.
+
+      Your friend and mine, Georg Brandl, made a lovely tool
+      called "add-to-pydotorg.py".  You can find it in the
+      "release" tree (next to "release.py").  You run the
+      tool on dl-files.iad1.psf.io, like this:
+
+      % AUTH_INFO=<username>:<python.org-api-key> python add-to-pydotorg.py <version>
+
+      This walks the correct download directory for <version>,
+      looks for files marked with <version>, and populates
+      the "Release Files" for the correct "release" on the web
+      site with these files.  Note that clears the "Release Files"
+      for the relevant version each time it's run.  You may run
+      it from any directory you like, and you can run it as
+      many times as you like if the files happen to change.
+      Keep a copy in your home directory on dl-files and
+      keep it fresh.
+
+      If new types of files are added to the release
+      (e.g. the web-based installers or redistributable zip
+      files added to Python 3.5) someone will need to update
+      add-to-pydotorg.py so it recognizes these new files.
+      (It's best to update add-to-pydotorg.py when file types
+      are removed, too.)
 
   ___ If this is a final release...
 
+      ___ XXX I didn't update this section yet.  I assume there are web site
+          changes to make for a final release...? XXX
+
       ___ Update the 'Quick Links' section on the front page.  Edit the
           top-level `content.ht` file.
 
@@ -522,16 +552,6 @@ How to Make A Release
 
       ___ Add the new version to `doc/versions/content.ht`.
 
-  ___ Add a news section item to the front page by editing newsindex.yml.  The
-      format should be pretty self evident.
-
-  ___ When everything looks good, `svn commit` in the data directory.  This
-      will trigger the live site to update itself, and at that point the
-      release is live.
-
-  ___ If this is a final release, create a new python.org/X.Y Apache alias
-      (or ask pydotorg to do so for you).
-
   Now it's time to write the announcement for the mailing lists.  This is the
   fuzzy bit because not much can be automated.  You can use an earlier
   announcement as a template, but edit it for content!

pep-0478.txt

@@ -46,11 +46,11 @@ The releases so far:
 - 3.5.0 beta 3: July 5, 2015
 - 3.5.0 beta 4: July 26, 2015
 - 3.5.0 release candidate 1: August 10, 2015
+- 3.5.0 release candidate 2: August 25, 2015
+- 3.5.0 release candidate 3: September 7, 2015
 
 Planned future release dates:
 
-- 3.5.0 release candidate 2: August 23, 2015
-- 3.5.0 release candidate 3: September 6, 2015
 - 3.5.0 final: September 13, 2015