X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/f0511c608866b3098e32a391b18c8cfd5bb0ceaa..27311cc77360e186bdfe9618193d531d0ea4e00d:/CHECKLST.txt diff --git a/CHECKLST.txt b/CHECKLST.txt index 9295b14d..efca86d9 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -53,6 +53,11 @@ Before tagging a release containing the word XXX-REVIEW-BEFORE-RELEASE. (Any such comments should state clearly what needs to be done.) + - Also, do some testing of the Windows version with Minefield, and + of the Unix version with valgrind or efence or both. In + particular, any headline features for the release should get a + workout with memory checking enabled! + 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 system on the compiler command line, and the _only_ place version @@ -101,7 +106,8 @@ This is the procedure I (SGT) currently follow (or _should_ follow of the tag. - Double-check that we have removed anything tagged with a comment - containing the word XXX-REMOVE-BEFORE-RELEASE. + containing the words XXX-REMOVE-BEFORE-RELEASE or + XXX-REVIEW-BEFORE-RELEASE. - Write a release announcement (basically a summary of the changes since the last release). Squirrel it away in @@ -160,7 +166,7 @@ of the tag. installer, and all signatures on the above. + top-level dir contains the Windows source zip (plus signatures), the Unix source tarball (plus signatures), - puttydoc.txt, the .hlp and .cnt files, and puttydoc.zip. + puttydoc.txt, the .hlp, .cnt and .chm files, and puttydoc.zip. - Create subdir `htmldoc' in the release directory, which should contain exactly the same set of HTML files that went into @@ -210,13 +216,6 @@ of the tag. Download page. + Adjust header text on Changelog page. (That includes changing `are new' in previous version to `were new'!) - + FOR 0.59 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. - + FOR 0.59 ONLY: update the Download page to remove all the Alpha - links. 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. @@ -231,9 +230,6 @@ of the tag. - Run webupdate, so that all the changes on ixion propagate to chiark. Important to do this _before_ announcing that the release is available. - * Don't forget to create the new directories on chiark - - ~/www/putty/{,/x86,/htmldoc} - before running - webupdate. - After running webupdate, run update-rsync on chiark and verify that the rsync mirror package correctly identifies the new