In local-to-remote copies, abort if fxp_init() fails, rather than ploughing

[PuTTY.git] / CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index fb630701e3e1038750681531db15ade2b2086ee6..522892ee275df48d4fe9b2a83ab8a41c8872b240 100644 (file)
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -46,8 +46,9 @@ The website:
 Before tagging a release
 ------------------------
 
- - First of all, go through the source and remove anything tagged
-   with a comment containing the word XXX-REMOVE-BEFORE-RELEASE.
+ - First of all, go through the source (including the documentation)
+   and remove anything tagged with a comment containing the word
+   XXX-REMOVE-BEFORE-RELEASE.
 
 For a long time we got away with never checking the current version
 number in at all - all version numbers were passed into the build
@@ -64,7 +65,8 @@ orders them correctly with respect to releases):
 
  - putty/LATEST.VER
 
-The Windows installer script (_three_ times, on consecutive lines):
+The Windows installer script (_three_ times, on consecutive lines,
+and again in a subsequent comment):
 
  - putty/windows/putty.iss
 
@@ -236,6 +238,8 @@ of the tag.
 
  - Announce the release!
     + Mail the announcement to putty-announce.
+       * Set a Reply-To on the mail so that people don't keep
+        replying to my personal address.
     + Post it to comp.security.ssh.
     + Mention it in <TDHTT> on mono.