git.distorted.org.uk Git - u/mdw/putty/blob - CHECKLST.txt

   1 Checklists for PuTTY administrative procedures
   2 ==============================================
   3
   4 Locations of the licence
   5 ------------------------
   6
   7 The PuTTY copyright notice and licence are stored in quite a few
   8 places. At the start of a new year, the copyright year needs
   9 updating in all of them; and when someone sends a massive patch,
  10 their name needs adding in all of them too.
  11
  12 The LICENCE file in the main source distribution:
  13
  14  - putty/LICENCE
  15
  16 The resource files:
  17
  18  - putty/pageant.rc
  19     + the copyright date appears twice, once in the About box and
  20       once in the Licence box. Don't forget to change both!
  21  - putty/puttygen.rc
  22     + the copyright date appears twice, once in the About box and
  23       once in the Licence box. Don't forget to change both!
  24  - putty/win_res.rc
  25     + the copyright date appears twice, once in the About box and
  26       once in the Licence box. Don't forget to change both!
  27  - putty/mac/mac_res.r
  28  - putty/unix/gtkdlg.c
  29     + the copyright date appears twice, once in the About box and
  30       once in the Licence box. Don't forget to change both!
  31
  32 The documentation (both the preamble blurb and the licence appendix):
  33
  34  - putty/doc/blurb.but
  35  - putty/doc/licence.but
  36
  37 The website:
  38
  39  - putty-website/licence.html
  40
  41 Before tagging a release
  42 ------------------------
  43
  44 For a long time we got away with never checking the current version
  45 number into CVS at all - all version numbers were passed into the
  46 build system on the compiler command line, and the _only_ place
  47 version numbers showed up in CVS was in the tag information.
  48
  49 Unfortunately, those halcyon days are gone, and we do need the
  50 version number in CVS in a couple of places. These must be updated
  51 _before_ tagging a new release.
  52
  53 The file used to generate the Unix snapshot version numbers (which
  54 are <previousrelease>-<date> so that the Debian versioning system
  55 orders them correctly with respect to releases):
  56
  57  - putty/LATEST.VER
  58
  59 The Windows installer script:
  60
  61  - putty/putty.iss
  62
  63 The Mac resource file (used to generate the binary bit of the 'vers'
  64 resources -- the strings are supplied by the usual means):
  65
  66  - putty/mac/version.r
  67
  68 It might also be worth going through the documentation looking for
  69 version numbers - we have a couple of transcripts showing the help
  70 text from the command-line tools, and it would be nice to ensure the
  71 whole transcripts (certainly including the version numbers) are up
  72 to date.
  73
  74  - putty/doc/pscp.but
  75  - putty/doc/plink.but
  76  - putty/doc/psftp.but (in case it ever acquires a similar thing)
  77
  78 The actual release procedure
  79 ----------------------------
  80
  81 This is the procedure I (SGT) currently follow (or _should_ follow
  82 :-) when actually making a release, once I'm happy with the position
  83 of the tag.
  84
  85  - Write a release announcement (basically a summary of the changes
  86    since the last release). Squirrel it away in
  87    ixion:src/putty/local/announce-<ver> in case it's needed again
  88    within days of the release going out.
  89
  90  - On my local machines, check out the release-tagged version of the
  91    sources.
  92     + Make sure to run mkfiles.pl _after_ this checkout, just in
  93       case.
  94
  95  - Build the Windows/x86 release binaries. Don't forget to supply
  96    VER=/DRELEASE=<ver>. Run them, or at least one or two of them, to
  97    ensure that they really do report their version number correctly.
  98     + Save the release link maps. Currently I keep these on ixion,
  99       in src/putty/local/maps-<version>.
 100
 101  - Acquire the Windows/alpha release binaries from Owen.
 102     + Verify the snapshot-key signatures on these, to ensure they're
 103       really the ones he built. If I'm going to snapshot-sign a zip
 104       file I make out of these, I'm damn well going to make sure the
 105       binaries that go _into_ it were snapshot-signed themselves.
 106     + Make sure Owen has kept the Alpha release link maps somewhere
 107       useful.
 108
 109  - Run Halibut to build the docs.
 110
 111  - Build the .zip files.
 112     + The binary archive putty.zip just contains all the .exe files
 113       except PuTTYtel, and the .hlp and .cnt files.
 114     + The source archive putty-src.zip is fiddly to build, so it's
 115       done by the shell script mksrcarc.sh. First check out the
 116       release sources in a pristine directory (to avoid cluttering
 117       the zip file with irrelevant stuff), then run mksrcarc.sh in
 118       that directory.
 119     + The docs archive puttydoc.zip contains all the HTML files
 120       output from Halibut.
 121
 122  - Build the installer.
 123
 124  - Sign the release (gpg --detach-sign).
 125     + Sign the locally built x86 binaries, the locally built x86
 126       binary zipfile, and the locally built x86 installer, with the
 127       release keys.
 128     + The Alpha binaries should already have been signed with the
 129       snapshot keys. Having checked that, sign the Alpha binary
 130       zipfile with the snapshot keys too.
 131     + The source archive should be signed with the release keys.
 132     + Don't forget to sign with both DSA and RSA keys for absolutely
 133       everything.
 134
 135  - Begin to pull together the release directory structure.
 136     + subdir `x86' containing the x86 binaries, x86 binary zip, x86
 137       installer, and all signatures on the above.
 138     + subdir `alpha' containing the Alpha binaries, Alpha binary
 139       zip, and all signatures on the above.
 140     + top-level dir contains the source zip (plus signatures),
 141       puttydoc.txt, the .hlp and .cnt files, and puttydoc.zip.
 142
 143  - Create and sign md5sums files: one in the x86 subdir, one in the
 144    alpha subdir, and one in the parent dir of both of those.
 145     + The md5sums files need not list the .DSA and .RSA signatures,
 146       and the top-level md5sums need not list the other two.
 147     + Sign the md5sums files (gpg --clearsign). The Alpha md5sums
 148       should be signed with the snapshot keys, but the other two
 149       with the release keys (yes, the top-level one includes some
 150       Alpha files, but I think people will understand).
 151
 152  - Now double-check by verifying all the signatures on all the
 153    files.
 154
 155  - Create subdir `htmldoc' in the release directory, which should
 156    contain exactly the same set of HTML files that went into
 157    puttydoc.zip.
 158     + It also needs a copy of sitestyle.css, because the online
 159       versions of the HTML docs will link to this (although the
 160       zipped form should be self-contained).
 161
 162  - Now the whole release directory should be present and correct.
 163    Upload to ixion:www/putty/<ver>, upload to
 164    chiark:ftp/putty-<ver>, and upload to the:www/putty/<ver>.
 165
 166  - Update the HTTP redirects.
 167     + Update the one at the:www/putty/htaccess which points the
 168       virtual subdir `latest' at the actual latest release dir. TEST
 169       THIS ONE - it's quite important.
 170     + ixion:www/putty/.htaccess has an individual redirect for each
 171       version number. Add a new one.
 172
 173  - Update the FTP symlink (chiark:ftp/putty-latest -> putty-<ver>).
 174
 175  - Update web site.
 176    + Adjust front page (`the latest version is <ver>').
 177    + Adjust Download page similarly.
 178    + Adjust filename of installer on links in Download page.
 179    + Adjust header text on Changelog page. (That includes changing
 180      `are new' in previous version to `were new'!)
 181
 182  - Update the wishlist - all items that have been fixed since the
 183    last release should have their "Fixed-in:" headers updated to
 184    include the release version number.
 185
 186  - Check the Docs page links correctly to the release docs. (It
 187    should do this automatically, owing to the `latest' HTTP
 188    redirect.)
 189
 190  - Check that the web server attaches the right content type to .HLP
 191    and .CNT files.
 192
 193  - Run webupdate, so that all the changes on ixion propagate to
 194    chiark. Important to do this _before_ announcing that the release
 195    is available.
 196
 197  - Announce the release!
 198     + Mail the announcement to putty-announce.
 199     + Post it to comp.security.ssh.
 200     + Mention it in <TDHIS> on mono.
 201
 202  - All done. Probably best to run `cvs up -A' now, or I'll only
 203    forget in a few days' time and get confused...