X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=CHECKLST.txt;h=063c480fade64278e8d2eda907bcf2f8047c69ad;hb=3a9b7ecaaa1eb07ff8b19e83c96f52d833313cbf;hp=ac5f3171c1bd641ad7b90c9a6558222f31b19ced;hpb=a28fe0e135c818dde5eb3fd81565346ea45a62df;p=PuTTY_svn.git diff --git a/CHECKLST.txt b/CHECKLST.txt index ac5f3171..063c480f 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! @@ -82,11 +76,6 @@ 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 @@ -115,21 +104,22 @@ of the tag. 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'. + 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. - - Move the release link maps out of the build directory and save - them somewhere more useful. Currently I keep these on ixion, in + - Save the link maps. Currently I keep these on ixion, in src/putty/local/maps-. - - Sign the release: type `./sign.sh build.out Releases', and enter - the passphrases a lot of times. + - 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 to ixion:www/putty/. + Upload it to ixion:www/putty/. - Do final checks on the release directory: + verify all the signatures: