- 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
- 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
----------------------------
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