Hmm, that relative link wasn't too good. Try a more helpful one.

[u/mdw/putty] / CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 9aca898..4022495 100644 (file)
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -25,6 +25,9 @@ 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
+ - 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!
 
 The documentation (both the preamble blurb and the licence appendix):
 
@@ -34,7 +37,7 @@ The documentation (both the preamble blurb and the licence appendix):
 The website:
 
  - putty-website/licence.html
- 
+
 Before tagging a release
 ------------------------
 
@@ -53,10 +56,25 @@ orders them correctly with respect to releases):
 
  - putty/LATEST.VER
 
-And the Windows installer script:
+The Windows installer script:
 
  - putty/putty.iss
 
+The Mac resource file (used to generate the binary bit of the 'vers'
+resources -- the strings are supplied by the usual means):
+
+ - putty/mac/version.r
+
+It might also be worth going through the documentation looking for
+version numbers - we have a couple of transcripts showing the help
+text from the command-line tools, and it would be nice to ensure the
+whole transcripts (certainly including the version numbers) are up
+to date.
+
+ - putty/doc/pscp.but
+ - putty/doc/plink.but
+ - putty/doc/psftp.but (in case it ever acquires a similar thing)
+
 The actual release procedure
 ----------------------------
 
@@ -71,16 +89,22 @@ of the tag.
 
  - On my local machines, check out the release-tagged version of the
    sources.
+    + Make sure to run mkfiles.pl _after_ this checkout, just in
+      case.
 
  - Build the Windows/x86 release binaries. Don't forget to supply
    VER=/DRELEASE=<ver>. Run them, or at least one or two of them, to
    ensure that they really do report their version number correctly.
+    + Save the release link maps. Currently I keep these on ixion,
+      in src/putty/local/maps-<version>.
 
  - Acquire the Windows/alpha release binaries from Owen.
     + Verify the snapshot-key signatures on these, to ensure they're
       really the ones he built. If I'm going to snapshot-sign a zip
       file I make out of these, I'm damn well going to make sure the
       binaries that go _into_ it were snapshot-signed themselves.
+    + Make sure Owen has kept the Alpha release link maps somewhere
+      useful.
 
  - Run Halibut to build the docs.
 
@@ -135,6 +159,9 @@ of the tag.
  - Create subdir `htmldoc' in the release directory, which should
    contain exactly the same set of HTML files that went into
    puttydoc.zip.
+    + It also needs a copy of sitestyle.css, because the online
+      versions of the HTML docs will link to this (although the
+      zipped form should be self-contained).
 
  - Now the whole release directory should be present and correct.
    Upload to ixion:www/putty/<ver>, upload to
@@ -162,6 +189,10 @@ of the tag.
  - Check that the web server attaches the right content type to .HLP
    and .CNT files.
 
+ - Run webupdate, so that all the changes on ixion propagate to
+   chiark. Important to do this _before_ announcing that the release
+   is available.
+
  - Announce the release!
     + Mail the announcement to putty-announce.
     + Post it to comp.security.ssh.