X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/8208b498c7693f48a86b2eb5c03175fb8935a4a1..b47d07f053b489ebd5afab1898dc29d4465ad8a9:/CHECKLST.txt?ds=sidebyside diff --git a/CHECKLST.txt b/CHECKLST.txt index 3b9eba3c..164e825e 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -25,6 +25,9 @@ The resource files: + 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 + - putty/unix/gtkdlg.c + + the copyright date appears twice, once in the About box and + once in the Licence box. Don't forget to change both! The documentation (both the preamble blurb and the licence appendix): @@ -34,7 +37,7 @@ The documentation (both the preamble blurb and the licence appendix): The website: - putty-website/licence.html - + Before tagging a release ------------------------ @@ -92,21 +95,27 @@ of the tag. - Build the Windows/x86 release binaries. Don't forget to supply VER=/DRELEASE=. Run them, or at least one or two of them, to ensure that they really do report their version number correctly. + + Save the release link maps. Currently I keep these on ixion, + in src/putty/local/maps-. - Acquire the Windows/alpha release binaries from Owen. + Verify the snapshot-key signatures on these, to ensure they're really the ones he built. If I'm going to snapshot-sign a zip file I make out of these, I'm damn well going to make sure the binaries that go _into_ it were snapshot-signed themselves. + + Make sure Owen has kept the Alpha release link maps somewhere + useful. - Run Halibut to build the docs. - Build the .zip files. + The binary archive putty.zip just contains all the .exe files except PuTTYtel, and the .hlp and .cnt files. - + The source archive putty-src.zip is built by puttysnap.sh (my - cron script that also builds the nightly snapshot source - archive). + + The source archive putty-src.zip is fiddly to build, so it's + done by the shell script mksrcarc.sh. First check out the + release sources in a pristine directory (to avoid cluttering + the zip file with irrelevant stuff), then run mksrcarc.sh in + that directory. + The docs archive puttydoc.zip contains all the HTML files output from Halibut. @@ -120,12 +129,6 @@ of the tag. snapshot keys. Having checked that, sign the Alpha binary zipfile with the snapshot keys too. + The source archive should be signed with the release keys. - This was the most fiddly bit of the last release I did: the - script that built the source archive was on ixion, so I had to - bring the archive back to my local machine, check everything - in it was untampered-with, and _then_ sign it. Perhaps next - time I should arrange that puttysnap.sh can run on my local - box; it'd be a lot easier. + Don't forget to sign with both DSA and RSA keys for absolutely everything. @@ -152,6 +155,9 @@ of the tag. - Create subdir `htmldoc' in the release directory, which should contain exactly the same set of HTML files that went into puttydoc.zip. + + It also needs a copy of sitestyle.css, because the online + versions of the HTML docs will link to this (although the + zipped form should be self-contained). - Now the whole release directory should be present and correct. Upload to ixion:www/putty/, upload to @@ -168,10 +174,15 @@ of the tag. - Update web site. + Adjust front page (`the latest version is '). + + Adjust Download page similarly. + Adjust filename of installer on links in Download page. + Adjust header text on Changelog page. (That includes changing `are new' in previous version to `were new'!) + - Update the wishlist - all items that have been fixed since the + last release should have their "Fixed-in:" headers updated to + include the release version number. + - Check the Docs page links correctly to the release docs. (It should do this automatically, owing to the `latest' HTTP redirect.)