projects
/
u
/
mdw
/
putty
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
`win-versioninfo': all builds of all Windows binaries now contain
[u/mdw/putty]
/
CHECKLST.txt
diff --git
a/CHECKLST.txt
b/CHECKLST.txt
index
61d37e1
..
608d578
100644
(file)
--- a/
CHECKLST.txt
+++ b/
CHECKLST.txt
@@
-21,9
+21,11
@@
The resource files:
- 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/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/windows/win_res.rc
+ - putty/windows/win_res.rc
2
+ 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/windows/version.rc2
+ + the copyright date appears once only.
- 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
+ the copyright date appears twice, once in the About box and
once in the Licence box. Don't forget to change both!
@@
-46,8
+48,9
@@
The website:
Before tagging a release
------------------------
Before tagging a release
------------------------
- - First of all, go through the source and remove anything tagged
- with a comment containing the word XXX-REMOVE-BEFORE-RELEASE.
+ - First of all, go through the source (including the documentation)
+ and remove anything tagged with a comment containing the word
+ XXX-REMOVE-BEFORE-RELEASE.
For a long time we got away with never checking the current version
number in at all - all version numbers were passed into the build
For a long time we got away with never checking the current version
number in at all - all version numbers were passed into the build
@@
-64,12
+67,18
@@
orders them correctly with respect to releases):
- putty/LATEST.VER
- putty/LATEST.VER
-The Windows installer script:
+The Windows installer script (_three_ times, on consecutive lines,
+and again in a subsequent comment):
- putty/windows/putty.iss
- 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)
+
The Mac resource file (used to generate the binary bit of the 'vers'
The Mac resource file (used to generate the binary bit of the 'vers'
-resources
-- the strings are supplied by the usual means
):
+resources):
- putty/mac/version.r
- putty/mac/version.r
@@
-112,7
+121,8
@@
of the tag.
- 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
- 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.
+ ensure that they really do report their version number correctly,
+ and sanity-check the version info reported on the files by Windows.
+ Save the release link maps. Currently I keep these on ixion,
in src/putty/local/maps-<version>.
+ Save the release link maps. Currently I keep these on ixion,
in src/putty/local/maps-<version>.
@@
-236,6
+246,8
@@
of the tag.
- Announce the release!
+ Mail the announcement to putty-announce.
- Announce the release!
+ Mail the announcement to putty-announce.
+ * Set a Reply-To on the mail so that people don't keep
+ replying to my personal address.
+ Post it to comp.security.ssh.
+ Mention it in <TDHTT> on mono.
+ Post it to comp.security.ssh.
+ Mention it in <TDHTT> on mono.