X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=CHECKLST.txt;h=dc1db5e0637ff22576f03f86b4898e58783f04fc;hb=f004bcca17a789356c32527a396b68b71a773db2;hp=99230f3625c2aa1a75e12124ede2e3f00621e732;hpb=0efa9febcaefb58ccd810a0aa8ed7b3a7f34db1c;p=PuTTY.git diff --git a/CHECKLST.txt b/CHECKLST.txt index 99230f36..dc1db5e0 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -71,11 +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) - 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 @@ -87,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 ---------------------------- @@ -103,10 +111,9 @@ of the tag. 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 @@ -136,13 +143,6 @@ of the tag. - Check the permissions! Actually try downloading from the, to make sure it really works. - - Update the website to refer to the new release: - + on the front page, add a news item. - + also on the front page, update the line that says "The latest - version is beta 0.XX". (This one's really important, because the - 'update-rsync' website mirror script on chiark greps for it!) - + write a section on the Changes page. - - Update the HTTP redirects. + Update the one at the:www/putty/htaccess which points the virtual subdir `latest' at the actual latest release dir. TEST @@ -153,10 +153,15 @@ of the tag. - 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'!) @@ -179,10 +184,13 @@ of the tag. subdirectory for the new version and mentions it in its .htaccess. - Announce the release! - + Mail the announcement to . - * Put a 'Reply-To: putty@projects.tartarus.org' header 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.