X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/6a9370de8ed0b9a46c4476a16b789e458ad671c9..a701fd77fbed86ec598bff07f212187cd41a260d:/CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 657d7759..bceaae64 100644
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -41,6 +41,9 @@ The website:
 Before tagging a release
 ------------------------
 
+ - First of all, go through the source and remove anything tagged
+   with a comment containing the word XXX-REMOVE-BEFORE-RELEASE.
+
 For a long time we got away with never checking the current version
 number into CVS at all - all version numbers were passed into the
 build system on the compiler command line, and the _only_ place
@@ -82,6 +85,9 @@ This is the procedure I (SGT) currently follow (or _should_ follow
 :-) when actually making a release, once I'm happy with the position
 of the tag.
 
+ - Double-check that we have removed anything tagged with a comment
+   containing the word XXX-REMOVE-BEFORE-RELEASE.
+
  - Write a release announcement (basically a summary of the changes
    since the last release). Squirrel it away in
    ixion:src/putty/local/announce-<ver> in case it's needed again
@@ -166,6 +172,9 @@ of the tag.
    Upload to ixion:www/putty/<ver>, upload to
    chiark:ftp/putty-<ver>, and upload to the:www/putty/<ver>.
 
+ - Check the permissions! Actually try downloading from the, to make
+   sure it really works.
+
  - Update the HTTP redirects.
     + Update the one at the:www/putty/htaccess which points the
       virtual subdir `latest' at the actual latest release dir. TEST
@@ -197,6 +206,10 @@ of the tag.
    chiark. Important to do this _before_ announcing that the release
    is available.
 
+ - After running webupdate, run update-rsync on chiark and verify
+   that the rsync mirror package correctly identifies the new
+   version.
+
  - Announce the release!
     + Mail the announcement to putty-announce.
     + Post it to comp.security.ssh.