Updates based on the Python 2.2.3 release. There may be more...

pep-0102.txt

@@ -78,6 +78,11 @@ How to Make A Release
       references to the release number.  As for the README file, changing
       these are necessary for a new micro, minor or major release.
 
+      The LICENSE fie contains a table that describes the legal
+      heritage of Python; you should add an entry for the X.Y.Z
+      release you are now making.  You should update this table in the
+      LICENSE file on the CVS trunk too.
+
   ___ When the year changes, copyright legends need to be updated in
       many places, including the README and LICENSE files.
 
@@ -147,21 +152,24 @@ How to Make A Release
   ___ Do a "cvs update" in this directory.  Do NOT include the -A flag!
 
       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.
+      and/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.
 
   ___ Now tag the branch using a symbolic name like "rXYMaZ",
       e.g. r212
       % cvs tag r212
 
+      Be sure to tag only the python/dist/src subdirectory of the
+      Python CVS tree!
+
   ___ Change to a neutral directory, i.e. one in which you can do a
       fresh, virgin, cvs export of the branch.  You will be creating a
       new directory at this location, to be named "Python-X.Y.M".  Do
       a CVS export of the tagged branch.
 
       % cd ~
-      % cvs -d <cvsroot> export -rr212 -d Python-2.1.2 python/dist/src
+      % cvs -d cvs.sf.net:/cvsroot/python export -rr212 -d Python-2.1.2 python/dist/src
 
   ___ Generate the tarball.  Note that we're not using the `z' option
       on the tar command because 1) that's only supported by GNU tar
@@ -204,44 +212,35 @@ How to Make A Release
   ___ While you're waiting, you can start twiddling the web pages to
       include the announcement.
 
-    ___ In the python.org web site CVS tree, cd to the X.Y
-        subdirectory, and copy index.ht to new-index.ht.  Be sure to
-        do a "cvs update" first!
+    ___ In the top of the python.org web site CVS tree, create a
+        subdirectory for the X.Y.Z release.  You can actually copy an
+        earlier patch release's subdirectory, but be sure to delete
+        the X.Y.Z/CVS directory and "cvs add X.Y.Z", for example:
 
         % cd .../pydotorg
-        % cvs -q up -P -d
-        % cd 2.2
-        % cp index.ht new-index.ht
+        % cp -r 2.2.2 2.2.3
+        % rm -rf 2.2.3/CVS
+        % cvs add 2.2.3
+        % cd 2.2.3
 
-    ___ Edit the file for content: usually you can globally replace
+    ___ Edit the files for content: usually you can globally replace
         X.Ya(Z-1) with X.YaZ.  However, you'll need to think about the
         "What's New?" section.
 
-    ___ Copy the Misc/NEWS file to NEWS.txt in the X.Y directory for
+    ___ Copy the Misc/NEWS file to NEWS.txt in the X.Y.Z directory for
         python.org; this contains the "full scoop" of changes to
         Python since the previous release for this version of Python.
 
-        If this is the first release in a series (e.g. 2.2.1c1) then
-        you'll need to create a new directory (e.g. 2.2.1).  It's
-        probably best to copy the last directory across:
-
-        % cp -r 2.2 2.2.1
-        % rm -rf 2.2.1/CVS
-        % cvs add 2.2.1
-
-        and then make changes as needed.  Verbiage from prereleases of
-        previous versions can be found in CVS if you're feeling uninspired.
-
     ___ Also, update the MD5 checksums.
 
-    ___ Preview the web page by doing a "make" -- NOT a "make install".
-        View the page via a file: url.
+    ___ Preview the web page by doing a "make" or "make install" (as
+        long as you've created a new directory for this release!)
 
     ___ Similarly, edit the ../index.ht file, i.e. the python.org home
         page.  In the Big Blue Announcement Block, move the paragraph
         for the new version up to the top and boldify the phrase
-        "Python X.YaZ is out".  Edit for content, and preview as
-        above.  Do NOT do a "make install" yet!
+        "Python X.YaZ is out".  Edit for content, and preview locally,
+        but do NOT do a "make install" yet!
 
   ___ Now we're waiting for the scp to creosote to finish.  Da de da,
       da de dum, hmm, hmm, dum de dum.
@@ -276,14 +275,9 @@ How to Make A Release
   ___ Update the X.Y/bugs.ht file if necessary.  It is best to get
       BDFL input for this step.
 
-  ___ Now preview the new-index.ht file once more.  IMPORTANT: follow
-      every link on the page to make sure it goes where you expect it
-      to go, and that what you expect to be there is there.
-
-  ___ If everything looks good, move new-index.ht to index.ht and do a
-      "make install" in this directory.  Go up to the parent directory
-      (i.e. the root of the web page hierarchy) and do a "make
-      install" there too.  You're release is now live!
+  ___ Go up to the parent directory (i.e. the root of the web page
+      hierarchy) and do a "make install" there.  You're release is now
+      live!
 
   ___ Now it's time to write the announcement for the mailing lists.
       This is the fuzzy bit because not much can be automated.  You