- - 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.
-
- - Do a bit of checking that the release binaries basically work,
- report their version numbers accurately, and so on. Test the
- installer and the Unix source tarball.
-
- - Save the link maps. Currently I keep these on atreus, in
- src/putty/local/maps-<version>.
-
- - Sign the release: in the `build.out' directory, type `./sign.sh
- putty Releases', and enter the passphrases a lot of times.
-
- - Now the whole release directory should be present and correct.
- Upload it to atreus:www/putty/<ver>.
-
- - Do final checks on the release directory:
- + verify all the signatures:
- for i in `find . -name '*.*SA'`; do case $i in *sums*) gpg --verify $i;; *) gpg --verify $i ${i%%.?SA};; esac; done
- + check the checksum files:
- md5sum -c md5sums
- sha1sum -c sha1sums
- sha256sum -c sha256sums
- sha512sum -c sha512sums
-
- - Having double-checked the release, copy it from atreus to
- chiark:ftp/putty-<ver> and 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
- THIS ONE - it's quite important.
- + atreus:www/putty/.htaccess has an individual redirect for each
- version number. Add a new one.
-
- - Update the FTP symlink (chiark:ftp/putty-latest -> putty-<ver>).
-
- - Update web site.
- + Adjust front page to say 'The latest version is <ver>'.
- + Adjust front page to add a news item.
- + Adjust Download page to say 'The latest release version (<ver>)'.
- + Adjust Download page to update filenames of installer and Unix
- tarball (both in the hrefs themselves and the link text).
- + Check over the Download page and remove any mention of
- pre-releases, if there were any before this release. Comment out
- the big pre-release section at the top, and also adjust the
- sections about source archives at the bottom.
- + Adjust header text on Changelog page. (That includes changing
- `are new' in previous version to `were new'!)
-
- - Update the wishlist. This can be done without touching individual
- items by editing the @releases array in control/bugs2html.
-
- - Check the Docs page links correctly to the release docs. (It
- should do this automatically, owing to the `latest' HTTP
- redirect.)
-
- - Check that the web server attaches the right content type to .HLP
- and .CNT files.