- 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.
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.
- 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/<ver>, upload to
- Update web site.
+ Adjust front page (`the latest version is <ver>').
+ + 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.)