- - Update the web site, in a local checkout.
- + 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'!)
- + .htaccess has an individual redirect for each version number. Add
- a new one.
-
- - If there are any last-minute wishlist entries (e.g. security
- vulnerabilities fixed in the new release), write entries for them
- in a local checkout of putty-wishlist.
-
- - Update the wishlist mechanism for the new release. This can be done
- without touching individual items by editing the @releases array in
- control/bugs2html.
-
- - Build the release, by checking out the release tag:
- git checkout 0.XX
- bob -F . RELEASE=0.XX
+ - Update the website, in a local checkout:
+ * Write a release file in components/releases which identifies the
+ new version, a section for the Changes page, and a news
+ announcement for the front page.
+ + The one thing this can't yet contain is the release date;
+ that has to be put in at the last minute, when the release
+ goes live. Fill in 'FIXME', for the moment.
+ * 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.
+
+ - Make a release-candidate build from the release tag, and put the
+ build.out and build.log dfiles somewhere safe. Normally I store
+ these in an adjacent directory, so I'll run a command like
+ bob -o ../X.YZ/build-X.YZ-rcN.out -l ../X.YZ/build-X.YZ-rcN.log -c X.YZ . RELEASE=X.YZ