X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=CHECKLST.txt;h=dc1db5e0637ff22576f03f86b4898e58783f04fc;hb=f004bcca17a789356c32527a396b68b71a773db2;hp=37b2de61a91fc1709f76a3dbc33af0d5c3f06c04;hpb=c4893477bdc563fd24cfeb406ff1925467670673;p=PuTTY.git diff --git a/CHECKLST.txt b/CHECKLST.txt index 37b2de61..dc1db5e0 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -26,12 +26,6 @@ The resource files: once in the Licence box. Don't forget to change both! - putty/windows/version.rc2 + the copyright date appears once only. - - 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! @@ -77,16 +71,6 @@ The Windows installer script (_four_ times, on consecutive lines): - putty/windows/putty.iss -The Windows resource file (used to generate the binary bit of the -VERSIONINFO resources -- the strings are supplied by the usual means): - - - putty/windows/version.rc2 (BASE_VERSION; NB, _comma_-separated) - -The Mac resource file (used to generate the binary bit of the 'vers' -resources): - - - putty/mac/version.r - It might also be worth going through the documentation looking for version numbers - we have a couple of transcripts showing the help text from the command-line tools, and it would be nice to ensure the @@ -98,6 +82,19 @@ it's worth grepping for that too. - putty/doc/plink.but - putty/doc/psftp.but (in case it ever acquires a similar thing) +Finally, reset the epoch used for the $(Days) value computed in +Buildscr for the Windows binary version resource. It's probably not a +good idea to set it to _today_ (since it might clash with the +zero-valued field used in actual releases), so perhaps we should start +it 1000 days before the release date so as to have a largish number +recognisable as being the right kind of thing by its order of +magnitude. So, do this: + + perl -e 'printf "%d\n", time/86400 - 1000' + +and then substitute the resulting value into the definition of 'Epoch' +in Buildscr. + The actual release procedure ---------------------------- @@ -111,34 +108,36 @@ of the tag. - Write a release announcement (basically a summary of the changes since the last release). Squirrel it away in - ixion:src/putty/local/announce- in case it's needed again + atreus:src/putty/local/announce- in case it's needed again within days of the release going out. - - Build the release: `bob putty-0.XX RELEASE=0.XX'. This should - generate a basically valid release directory as - `build.out/putty', and provide link maps and sign.sh alongside - that in build.out. + - Build the release: `bob -b 0.XX putty RELEASE=0.XX'. This should + generate a basically valid release directory as `build.out/putty', + and provide link maps and sign.sh alongside that in build.out. - Do a bit of checking that the release binaries basically work, report their version numbers accurately, and so on. Test the installer and the Unix source tarball. - - Save the link maps. Currently I keep these on ixion, in + - Save the link maps. Currently I keep these on atreus, in src/putty/local/maps-. - Sign the release: in the `build.out' directory, type `./sign.sh putty Releases', and enter the passphrases a lot of times. - Now the whole release directory should be present and correct. - Upload it to ixion:www/putty/. + Upload it to atreus:www/putty/. - Do final checks on the release directory: + verify all the signatures: - for i in `find . -name '*.*SA'`; do case $i in *md5sums*) gpg --verify $i;; *) gpg --verify $i ${i%%.?SA};; esac; done - + check the md5sums: + for i in `find . -name '*.*SA'`; do case $i in *sums*) gpg --verify $i;; *) gpg --verify $i ${i%%.?SA};; esac; done + + check the checksum files: md5sum -c md5sums + sha1sum -c sha1sums + sha256sum -c sha256sums + sha512sum -c sha512sums - - Having double-checked the release, copy it from ixion to + - Having double-checked the release, copy it from atreus to chiark:ftp/putty- and to the:www/putty/. - Check the permissions! Actually try downloading from the, to make @@ -148,16 +147,21 @@ of the tag. + Update the one at the:www/putty/htaccess which points the virtual subdir `latest' at the actual latest release dir. TEST THIS ONE - it's quite important. - + ixion:www/putty/.htaccess has an individual redirect for each + + atreus:www/putty/.htaccess has an individual redirect for each version number. Add a new one. - Update the FTP symlink (chiark:ftp/putty-latest -> putty-). - Update web site. - + Adjust front page (`the latest version is '). - + Adjust Download page similarly. - + Adjust filenames of installer and Unix tarball on links in - Download page. + + Adjust front page to say 'The latest version is '. + + Adjust front page to add a news item. + + Adjust Download page to say 'The latest release version ()'. + + Adjust Download page to update filenames of installer and Unix + tarball (both in the hrefs themselves and the link text). + + Check over the Download page and remove any mention of + pre-releases, if there were any before this release. Comment out + the big pre-release section at the top, and also adjust the + sections about source archives at the bottom. + Adjust header text on Changelog page. (That includes changing `are new' in previous version to `were new'!) @@ -171,18 +175,22 @@ of the tag. - Check that the web server attaches the right content type to .HLP and .CNT files. - - Run webupdate, so that all the changes on ixion propagate to + - Run webupdate, so that all the changes on atreus propagate to chiark. Important to do this _before_ announcing that the release is available. - - After running webupdate, run update-rsync on chiark and verify - that the rsync mirror package correctly identifies the new - version. + - After running webupdate, run update-rsync on chiark and verify that + the rsync mirror package (~/ftp/putty-website-mirror) contains a + subdirectory for the new version and mentions it in its .htaccess. - 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. + + Construct a release announcement email whose message body is the + announcement written above, and which includes the following + headers: + * Reply-To: + * Subject: PuTTY X.YZ is released + + Mail that release announcement to + . + Post it to comp.security.ssh. + Mention it in on mono.