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.
+
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
:-) when actually making a release, once I'm happy with the position
of the tag.
+ - Double-check that we have removed anything tagged with a comment
+ containing the word XXX-REMOVE-BEFORE-RELEASE.
+
- Write a release announcement (basically a summary of the changes
since the last release). Squirrel it away in
ixion:src/putty/local/announce-<ver> in case it's needed again
Upload to ixion:www/putty/<ver>, upload to
chiark:ftp/putty-<ver>, and upload to the:www/putty/<ver>.
+ - Check the permissions! Actually try downloading from the, to make
+ sure it really works.
+
- Update the HTTP redirects.
+ Update the one at the:www/putty/htaccess which points the
virtual subdir `latest' at the actual latest release dir. TEST
chiark. Important to do this _before_ announcing that the release
is available.
+ - After running webupdate, run update-rsync on chiark and verify
+ that the rsync mirror package correctly identifies the new
+ version.
+
- Announce the release!
+ Mail the announcement to putty-announce.
+ Post it to comp.security.ssh.