X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=CHECKLST.txt;h=522892ee275df48d4fe9b2a83ab8a41c8872b240;hb=93712a3ee16b68d3cc70dbd144101e7eb0183a08;hp=2fd470f562cac72de41173fa260f161c7ac3fb3e;hpb=a7c8747e0da4f8f88bf78825b4a9c654ad1c55c3;p=PuTTY.git diff --git a/CHECKLST.txt b/CHECKLST.txt index 2fd470f5..522892ee 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -15,16 +15,21 @@ The LICENCE file in the main source distribution: The resource files: - - putty/pageant.rc + - putty/windows/pageant.rc + the copyright date appears twice, once in the About box and once in the Licence box. Don't forget to change both! - - putty/puttygen.rc + - putty/windows/puttygen.rc + the copyright date appears twice, once in the About box and once in the Licence box. Don't forget to change both! - - putty/win_res.rc + - putty/windows/win_res.rc + the copyright date appears twice, once in the About box and once in the Licence box. Don't forget to change both! - putty/mac/mac_res.r + + the copyright date appears twice, once in the About box and + once in the Licence box. Don't forget to change both! + - putty/mac/macpgen.r + + the copyright date appears twice, once in the About box and + once in the Licence box. Don't forget to change both! - putty/unix/gtkdlg.c + the copyright date appears twice, once in the About box and once in the Licence box. Don't forget to change both! @@ -41,16 +46,17 @@ The website: Before tagging a release ------------------------ - - First of all, go through the source 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 remove anything tagged with a comment containing the word + XXX-REMOVE-BEFORE-RELEASE. For a long time we got away with never checking the current version -number into CVS at all - all version numbers were passed into the -build system on the compiler command line, and the _only_ place -version numbers showed up in CVS was in the tag information. +number in at all - all version numbers were passed into the build +system on the compiler command line, and the _only_ place version +numbers showed up in the source files was in the tag information. Unfortunately, those halcyon days are gone, and we do need the -version number in CVS in a couple of places. These must be updated +version number checked in in a couple of places. These must be updated _before_ tagging a new release. The file used to generate the Unix snapshot version numbers (which @@ -59,9 +65,10 @@ orders them correctly with respect to releases): - putty/LATEST.VER -The Windows installer script: +The Windows installer script (_three_ times, on consecutive lines, +and again in a subsequent comment): - - putty/putty.iss + - putty/windows/putty.iss The Mac resource file (used to generate the binary bit of the 'vers' resources -- the strings are supplied by the usual means): @@ -119,7 +126,10 @@ of the tag. + Make sure Owen has kept the Alpha release link maps somewhere useful. - - Run Halibut to build the docs. + - 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" - Build the binary archives putty.zip (one for each architecture): each one just contains all the .exe files except PuTTYtel, and @@ -154,6 +164,13 @@ of the tag. signatures), the Unix source tarball (plus signatures), puttydoc.txt, the .hlp and .cnt files, and puttydoc.zip. + - 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). + - Create and sign md5sums files: one in the x86 subdir, one in the alpha subdir, and one in the parent dir of both of those. + The md5sums files need not list the .DSA and .RSA signatures, @@ -166,13 +183,6 @@ of the tag. - Now double-check by verifying all the signatures on all the files, and running md5sum -c on all the md5sums files. - - 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/. @@ -228,6 +238,8 @@ of the tag. - Announce the release! + Mail the announcement to putty-announce. + * Set a Reply-To on the mail so that people don't keep + replying to my personal address. + Post it to comp.security.ssh. + Mention it in on mono. @@ -239,5 +251,5 @@ After the release The following want doing some time soon after a release has been made: - If the release was made from a branch, make sure the version number - in _trunk_ CVS is up to date in all the locations listed above, so + on the _trunk_ is up to date in all the locations listed above, so that (e.g.) Unix snapshots come out right.