X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/6e7a48828dc13d077e278df1c0598f6bfa66ef0b..8c6abd046affdf1fcfc719a7f73ba46565d6dc0c:/CHECKLST.txt diff --git a/CHECKLST.txt b/CHECKLST.txt index 40224951..164e825e 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -111,9 +111,11 @@ of the tag. - 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. @@ -127,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. @@ -178,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.)