Before tagging a release
------------------------
- - First of all, go through the source (including the documentation)
- and remove anything tagged with a comment containing the word
- XXX-REMOVE-BEFORE-RELEASE.
+ - First of all, go through the source (including the documentation),
+ and the website, and review anything tagged with a comment
+ containing the word XXX-REVIEW-BEFORE-RELEASE.
+ (Any such comments should state clearly what needs to be done.)
For a long time we got away with never checking the current version
number in at all - all version numbers were passed into the build
- Run Halibut to build the docs. Define VERSION on the make command
line to override the version strings, since Subversion revision
numbers are less meaningful on a tag.
- + make -C doc VERSION="PuTTY release 0.XX"
+ + change into the doc subdir
+ + run `make VERSION="PuTTY release 0.XX" chm', then run `hhc
+ putty.hhp' to build the .CHM
+ + then run `make mostlyclean' (destroys the hhc input files but
+ _not_ the .CHM)
+ + then `make VERSION="PuTTY release 0.XX"'
- Build the binary archives putty.zip (one for each architecture):
each one just contains all the .exe files except PuTTYtel, and
Download page.
+ Adjust header text on Changelog page. (That includes changing
`are new' in previous version to `were new'!)
+ + FOR NEXT RELEASE ONLY: update the docs page so that it links to
+ the release .chm as well as the release .hlp and .cnt. Remove
+ this checklist item after it's done; it won't need doing again
+ in the subsequent release.
- Update the wishlist. This can be done without touching individual
items by editing the @releases array in control/bugs2html.
~mdw / sgt / putty / blobdiff