simon-git: putty (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  267f077f Reorganise the release checklist.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2025-02-08 11:29:39

commit 267f077fcc07ff27cd3a4cad80ccece30f65bfb8
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=267f077fcc07ff27cd3a4cad80ccece30f65bfb8;hp=edd9df9b3d945a5617649b5ef1bef7e5c83bf4f9
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Feb 8 11:26:25 2025 +0000

    Reorganise the release checklist.
    
    After all these years, this checklist is _still_ hard for me to get
    right. In the 0.83 runup this month, I prepared everything about the
    RC build in advance, but nothing about the announcements, website
    updates etc, and had to do all of that on release day.
    
    So I've completely removed the section "Preparing to make the
    release", which was ambiguous about whether it's done in advance or on
    the day. Now all the text parts (website, wishlist, announcements) are
    folded into the "make a release candidate" section, in the hope that
    I'll remember to do them all at the same time, which should mean
    
     - people have a few days to review the text _and_ test the RC build
     - because they go together, I also remember to revise the text if a
       new RC build is needed (e.g. mention whatever extra fix it has).
    
    The "actual release procedure" section is now down to _only_ the
    things I have to do on the day, which is basically uploading
    everything, going live, and communicating the release.

 CHECKLST.txt | 80 +++++++++++++++++++++++++++++++-----------------------------
 1 file changed, 42 insertions(+), 38 deletions(-)