From 70fd02153309c276368e8b0bf1c2210588d3ceab Mon Sep 17 00:00:00 2001 From: simon Date: Sun, 24 Dec 2006 16:25:30 +0000 Subject: [PATCH] Add some CHM-related stuff to the release checklist. Don't want to forget about it when the time comes. git-svn-id: svn://svn.tartarus.org/sgt/putty@7012 cda61777-01e9-0310-a592-d414129be87e --- CHECKLST.txt | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/CHECKLST.txt b/CHECKLST.txt index cc2dcf92..454bc180 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -137,7 +137,13 @@ of the tag. - 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 move the .CHM somewhere else so `make clean' doesn't blow + it away + + then run `make clean' + + 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 @@ -222,6 +228,10 @@ of the tag. 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. -- 2.11.0