From 9bea08a298580c98889834cbaffe289301753989 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 25 Jul 2015 11:28:32 +0100 Subject: [PATCH] Post-0.65 release checklist updates. The -F option is no longer needed to bob in this situation; that hasn't been the directory I keep release announcements in for a long time; the Docs page needs adjusting for pre-release retirement as well as the Downloads page. --- CHECKLST.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CHECKLST.txt b/CHECKLST.txt index da3f2542..d23b3f4e 100644 --- a/CHECKLST.txt +++ b/CHECKLST.txt @@ -93,7 +93,7 @@ for it: - Write a release announcement (basically a summary of the changes since the last release). Squirrel it away in - atreus:src/putty/local/announce- in case it's needed again + atreus:src/putty-local/announce- in case it's needed again within days of the release going out. - Update the web site, in a local checkout. @@ -106,6 +106,7 @@ for it: 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. + + Do the same on the Docs page. + Adjust header text on Changelog page. (That includes changing `are new' in previous version to `were new'!) + .htaccess has an individual redirect for each version number. Add @@ -121,7 +122,7 @@ for it: - Build the release, by checking out the release tag: git checkout 0.XX - bob -F . RELEASE=0.XX + bob . 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.