Check the x argument to check_boundary() more carefully.

[PuTTY.git] / CHECKLST.txt

diff --git a/CHECKLST.txt b/CHECKLST.txt
index d23b3f4e8159e0c963d7ad1a7adda94daee1e059..78e9d22317bf5e0a7e0b838d904449246fb60e62 100644 (file)
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -112,6 +112,11 @@ for it:
    + .htaccess has an individual redirect for each version number. Add
      a new one.
 
+ - For 0.66 only: if it's not already done, switch the remaining
+   signature links on the Download page over to using the new
+   signature style. Then remove this checklist item, since it'll only
+   need doing this once.
+
  - If there are any last-minute wishlist entries (e.g. security
    vulnerabilities fixed in the new release), write entries for them
    in a local checkout of putty-wishlist.
@@ -135,7 +140,7 @@ for it:
    installer and the Unix source tarball.
 
  - Sign the release: in the `build.out' directory, type
-     sh sign.sh putty Releases
+     sh sign.sh -r putty
    and enter the passphrases a lot of times.
 
 The actual release procedure
@@ -151,7 +156,7 @@ locally, this is the procedure for putting it up on the web.
 
  - Do final checks on the release directory in its new location:
     + verify all the signatures:
-      for i in `find . -name '*.*SA'`; do case $i in *sums*) gpg --verify $i;; *) gpg --verify $i ${i%%.?SA};; esac; done
+      for i in `find . -name '*.gpg'`; do case $i in *sums*) gpg --verify $i;; *) gpg --verify $i ${i%%.gpg};; esac; done
     + check the checksum files:
       md5sum -c md5sums
       sha1sum -c sha1sums