simon-git: putty (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  4624115 Make -DMINEFIELD show up in Windows buildinfo.
  ea0ab1c Simplify running of release.pl --setver.
  5cac601 Rework the release checklist for current practice.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2017-07-03 07:45:46

commit 4624115b76903b0b9ad97bee713afafcbd70a31c
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=4624115b76903b0b9ad97bee713afafcbd70a31c;hp=4065b0cd7888aa32664a76a29e1a7f95b54d656f
Author: Simon Tatham <anakin at pobox.com>
Date:   Mon Jul 3 07:27:05 2017 +0100

    Make -DMINEFIELD show up in Windows buildinfo.
    
    I listed a lot of other build options, but not that one. The release
    checklist still recommends doing test builds with it, so it seems
    sensible to arrange that you can tell if a build _is_ one of those or
    not.

 misc.c | 3 +++
 1 file changed, 3 insertions(+)

commit ea0ab1c8218f28957b6e20dd84f9d2a3f19313e6
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=ea0ab1c8218f28957b6e20dd84f9d2a3f19313e6;hp=4624115b76903b0b9ad97bee713afafcbd70a31c
Author: Simon Tatham <anakin at pobox.com>
Date:   Mon Jul 3 07:19:07 2017 +0100

    Simplify running of release.pl --setver.
    
    Previously, it demanded that your checkout was in a state where you
    had run autoconf but not configure; so if you previously did have a
    Makefile then you had to 'make distclean' to remove it, whereas if you
    previously had no generated files at all (e.g. starting from a
    completely clean checkout) then you had to run mkfiles.pl and
    mkauto.sh to generate 'configure'.
    
    This is obviously confusing, and moreover, the dependence on prior
    generated files is fragile and prone to them having been generated
    wrong. Adjusted the script so that it uses 'git archive' to get a
    clean directory containing only the version-controlled files, and then
    runs scripts itself to get that directory into the state it wants.

 CHECKLST.txt | 1 -
 release.pl   | 7 +++++--
 2 files changed, 5 insertions(+), 3 deletions(-)

commit 5cac6013b702b014a063ed98ad91128308bc1b48
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=5cac6013b702b014a063ed98ad91128308bc1b48;hp=ea0ab1c8218f28957b6e20dd84f9d2a3f19313e6
Author: Simon Tatham <anakin at pobox.com>
Date:   Mon Jul 3 07:38:20 2017 +0100

    Rework the release checklist for current practice.
    
    In recent releases we've taken to making the actual release build (or
    rather, candidates for it) ahead of time so that we can do some
    slightly more thorough last-minute testing of the exact binaries that
    we're going to release to everyone. It's time I actually wrote that
    procedure down in the checklist, so that I remember what it is.
    
    In particular, we had the idea that we should not properly GPG-sign
    the release until the last moment, and use the presence of a set of
    full GPG signatures as a means of distinguishing the real release
    build from an RC that accidentally got out into the wild somehow. This
    checklist update formalises that too, and documents the method I used
    of ensuring the binaries weren't tampered with between RC building and
    release signing (by making a signature on just the sha512sums). I also
    include in this commit an extra command-line option to sign.sh to make
    that preliminary signature step more convenient.

 CHECKLST.txt | 104 ++++++++++++++++++++++++++++++++++++-----------------------
 sign.sh      |  43 ++++++++++++++++++------
 2 files changed, 97 insertions(+), 50 deletions(-)