- - 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>.
+ - Update the website, in a local checkout:
+ * Write a release file in components/releases which identifies the
+ new version, its release date, a section for the Changes page,
+ and a news announcement for the front page.
+ * Disable the pre-release sections of the website (if previously
+ enabled), by editing prerel_version() in components/Base.mc to
+ return undef.
+
+ - Update the wishlist, in a local checkout:
+ * If there are any last-minute wishlist entries (e.g. security
+ vulnerabilities fixed in the new release), write entries for
+ them.
+ * If any other bug fixes have been cherry-picked to the release
+ branch (so that the wishlist mechanism can't automatically mark
+ them as fixed in the new release), add appropriate Fixed-in
+ headers for those.
+ * Add an entry to the @releases array in control/bugs2html.
+
+ - Build the release, by checking out the release tag:
+ git checkout 0.XX
+ bob . 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.
+
+ - Double-check in build.log that the release was built from the right
+ git commit.
+
+ - Do a bit of checking of the release binaries:
+ * make sure they basically work
+ * check they report the right version number
+ * if there's any easily observable behaviour difference between
+ the release branch and master, arrange to observe it
+ * test the Windows installer
+ * test the Unix source tarball.
+
+ - Sign the release: in the `build.out' directory, type
+ sh sign.sh -r putty
+ and enter the passphrases a lot of times.