Fix handle leak in winhandl.c.

[PuTTY.git] / CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index e131500ff29ccab3ff53e0d5ce498c4542d8166d..dc1db5e0637ff22576f03f86b4898e58783f04fc 100644 (file)
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -71,11 +71,6 @@ The Windows installer script (_four_ times, on consecutive lines):
 
  - putty/windows/putty.iss
 
-The Windows resource file (used to generate the binary bit of the
-VERSIONINFO resources -- the strings are supplied by the usual means):
-
- - putty/windows/version.rc2 (BASE_VERSION; NB, _comma_-separated)
-
 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
@@ -87,6 +82,19 @@ it's worth grepping for that too.
  - putty/doc/plink.but
  - putty/doc/psftp.but (in case it ever acquires a similar thing)
 
+Finally, reset the epoch used for the $(Days) value computed in
+Buildscr for the Windows binary version resource. It's probably not a
+good idea to set it to _today_ (since it might clash with the
+zero-valued field used in actual releases), so perhaps we should start
+it 1000 days before the release date so as to have a largish number
+recognisable as being the right kind of thing by its order of
+magnitude. So, do this:
+
+  perl -e 'printf "%d\n", time/86400 - 1000'
+
+and then substitute the resulting value into the definition of 'Epoch'
+in Buildscr.
+
 The actual release procedure
 ----------------------------
 
@@ -103,10 +111,9 @@ of the tag.
    atreus:src/putty/local/announce-<ver> in case it's needed again
    within days of the release going out.
 
- - Build the release: `bob putty-0.XX RELEASE=0.XX'. This should
-   generate a basically valid release directory as
-   `build.out/putty', and provide link maps and sign.sh alongside
-   that in build.out.
+ - Build the release: `bob -b 0.XX putty RELEASE=0.XX'. This should
+   generate a basically valid release directory as `build.out/putty',
+   and provide link maps and sign.sh alongside that in build.out.
 
  - Do a bit of checking that the release binaries basically work,
    report their version numbers accurately, and so on. Test the
@@ -177,10 +184,13 @@ of the tag.
    subdirectory for the new version and mentions it in its .htaccess.
 
  - Announce the release!
-    + Mail the announcement to <putty-announce@lists.tartarus.org>.
-       * Put a 'Reply-To: putty@projects.tartarus.org' header on the
-        mail so that people don't keep replying to my personal
-        address.
+    + Construct a release announcement email whose message body is the
+      announcement written above, and which includes the following
+      headers:
+       * Reply-To: <putty@projects.tartarus.org>
+       * Subject: PuTTY X.YZ is released
+    + Mail that release announcement to
+      <putty-announce@lists.tartarus.org>.
     + Post it to comp.security.ssh.
     + Mention it in <TDHTT> on mono.