X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/a0214f4d43d1aa4e771a94dca61b849608f8a007..4e95a413c2909c807226e5efc09da4c8ba24740e:/CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 2be089e3..522892ee 100644
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -25,6 +25,11 @@ The resource files:
     + the copyright date appears twice, once in the About box and
       once in the Licence box. Don't forget to change both!
  - putty/mac/mac_res.r
+    + the copyright date appears twice, once in the About box and
+      once in the Licence box. Don't forget to change both!
+ - putty/mac/macpgen.r
+    + the copyright date appears twice, once in the About box and
+      once in the Licence box. Don't forget to change both!
  - putty/unix/gtkdlg.c
     + the copyright date appears twice, once in the About box and
       once in the Licence box. Don't forget to change both!
@@ -41,8 +46,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.
+ - First of all, go through the source (including the documentation)
+   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 in at all - all version numbers were passed into the build
@@ -59,7 +65,8 @@ orders them correctly with respect to releases):
 
  - putty/LATEST.VER
 
-The Windows installer script:
+The Windows installer script (_three_ times, on consecutive lines,
+and again in a subsequent comment):
 
  - putty/windows/putty.iss
 
@@ -119,7 +126,10 @@ of the tag.
     + Make sure Owen has kept the Alpha release link maps somewhere
       useful.
 
- - Run Halibut to build the docs.
+ - Run Halibut to build the docs. Define VERSION on the make command
+   line to override the version strings, since Subversion revision
+   numbers are less meaningful on a tag.
+    + make -C doc VERSION="PuTTY release 0.XX"
 
  - Build the binary archives putty.zip (one for each architecture):
    each one just contains all the .exe files except PuTTYtel, and
@@ -228,6 +238,8 @@ of the tag.
 
  - Announce the release!
     + Mail the announcement to putty-announce.
+       * Set a Reply-To on the mail so that people don't keep
+	 replying to my personal address.
     + Post it to comp.security.ssh.
     + Mention it in <TDHTT> on mono.