uint64_decimal() incorrectly output 0 as "" instead of "0". This only affected

[u/mdw/putty] / CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index ccc0ef0..5c6d2cf 100644 (file)
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -15,13 +15,13 @@ The LICENCE file in the main source distribution:
 
 The resource files:
 
 
 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!
     + 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!
     + 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
     + 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
    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
 
 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
 _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:
 
 
 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):
 
 The Mac resource file (used to generate the binary bit of the 'vers'
 resources -- the strings are supplied by the usual means):


@@ -119,7 +119,10 @@ of the tag.
     + Make sure Owen has kept the Alpha release link maps somewhere
       useful.
 
     + 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
 
  - Build the binary archives putty.zip (one for each architecture):
    each one just contains all the .exe files except PuTTYtel, and


@@ -239,5 +242,5 @@ 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
 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

-   in _trunk_ CVS is up to date in all the locations listed above, so
+   on the _trunk_ is up to date in all the locations listed above, so

    that (e.g.) Unix snapshots come out right.
    that (e.g.) Unix snapshots come out right.