X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=CHECKLST.txt;h=6e775f9aa2cd1453ea8581be1da9e37df47fada0;hb=12e019bafc75cb441e965c63e15dfceeaf71ca1e;hp=9295b14dff0aa7f76161a201db262653badfd3ba;hpb=ae1c3746670e04c932fb7f053af41023014975f4;p=PuTTY.git

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 9295b14d..6e775f9a 100644
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -101,7 +101,8 @@ This is the procedure I (SGT) currently follow (or _should_ follow
 of the tag.
 
  - Double-check that we have removed anything tagged with a comment
-   containing the word XXX-REMOVE-BEFORE-RELEASE.
+   containing the words XXX-REMOVE-BEFORE-RELEASE or
+   XXX-REVIEW-BEFORE-RELEASE.
 
  - Write a release announcement (basically a summary of the changes
    since the last release). Squirrel it away in
@@ -160,7 +161,7 @@ of the tag.
       installer, and all signatures on the above.
     + top-level dir contains the Windows source zip (plus
       signatures), the Unix source tarball (plus signatures),
-      puttydoc.txt, the .hlp and .cnt files, and puttydoc.zip.
+      puttydoc.txt, the .hlp, .cnt and .chm files, and puttydoc.zip.
 
  - Create subdir `htmldoc' in the release directory, which should
    contain exactly the same set of HTML files that went into
@@ -210,13 +211,6 @@ of the tag.
      Download page.
    + Adjust header text on Changelog page. (That includes changing
      `are new' in previous version to `were new'!)
-   + FOR 0.59 ONLY: update the docs page so that it links to the
-     release .chm as well as the release .hlp and .cnt. Remove this
-     checklist item after it's done; it won't need doing again in
-     the subsequent release.
-   + FOR 0.59 ONLY: update the Download page to remove all the Alpha
-     links. Remove this checklist item after it's done; it won't
-     need doing again in the subsequent release.
 
  - Update the wishlist. This can be done without touching individual
    items by editing the @releases array in control/bugs2html.
@@ -231,9 +225,6 @@ of the tag.
  - Run webupdate, so that all the changes on ixion propagate to
    chiark. Important to do this _before_ announcing that the release
    is available.
-    * Don't forget to create the new directories on chiark -
-      ~/www/putty/<ver>{,/x86,/htmldoc} - before running
-      webupdate.
 
  - After running webupdate, run update-rsync on chiark and verify
    that the rsync mirror package correctly identifies the new