X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/d50c1c624c37205105ac9d2507d6b32e6395e900..e693a2d9c8385b9177a24e28ab63701973975919:/CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 9a55504c..5c6d2cf1 100644
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -15,13 +15,13 @@ The LICENCE file in the main source distribution:
 
 The resource files:
 
- - putty/pageant.rc
+ - putty/windows/pageant.rc
     + the copyright date appears twice, once in the About box and
       once in the Licence box. Don't forget to change both!
- - putty/puttygen.rc
+ - putty/windows/puttygen.rc
     + the copyright date appears twice, once in the About box and
       once in the Licence box. Don't forget to change both!
- - putty/win_res.rc
+ - putty/windows/win_res.rc
     + 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
@@ -45,12 +45,12 @@ Before tagging a release
    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
-version numbers showed up in CVS was in the tag information.
+number in at all - all version numbers were passed into the build
+system on the compiler command line, and the _only_ place version
+numbers showed up in the source files was in the tag information.
 
 Unfortunately, those halcyon days are gone, and we do need the
-version number in CVS in a couple of places. These must be updated
+version number checked in in a couple of places. These must be updated
 _before_ tagging a new release.
 
 The file used to generate the Unix snapshot version numbers (which
@@ -61,7 +61,7 @@ orders them correctly with respect to releases):
 
 The Windows installer script:
 
- - putty/putty.iss
+ - putty/windows/putty.iss
 
 The Mac resource file (used to generate the binary bit of the 'vers'
 resources -- the strings are supplied by the usual means):
@@ -72,7 +72,8 @@ 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.
+to date. Sometimes these are marked in between releases as `0.XX', so
+it's worth grepping for that too.
 
  - putty/doc/pscp.but
  - putty/doc/plink.but
@@ -118,7 +119,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
@@ -153,6 +157,13 @@ of the tag.
       signatures), the Unix source tarball (plus signatures),
       puttydoc.txt, the .hlp and .cnt files, and puttydoc.zip.
 
+ - 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).
+
  - Create and sign md5sums files: one in the x86 subdir, one in the
    alpha subdir, and one in the parent dir of both of those.
     + The md5sums files need not list the .DSA and .RSA signatures,
@@ -165,13 +176,6 @@ of the tag.
  - Now double-check by verifying all the signatures on all the
    files, and running md5sum -c on all the md5sums files.
 
- - 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>.
 
@@ -230,4 +234,13 @@ of the tag.
     + Post it to comp.security.ssh.
     + Mention it in <TDHTT> on mono.
 
- - All done.
+ - Relax (slightly).
+
+After the release
+-----------------
+
+The following want doing some time soon after a release has been made:
+
+ - If the release was made from a branch, make sure the version number
+   on the _trunk_ is up to date in all the locations listed above, so
+   that (e.g.) Unix snapshots come out right.