From: simon <simon@cda61777-01e9-0310-a592-d414129be87e>
Date: Fri, 26 Jan 2007 14:11:56 +0000 (+0000)
Subject: If I'd tested under Minefield before releasing, r7168 would have
X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/commitdiff_plain/ed1829a3d9374e1fcabfc270e9129c68b8b269ab?hp=45d56852d8bd85126c66fb93fcc7a4c527a697b1

If I'd tested under Minefield before releasing, r7168 would have
been committed before the release. Therefore, stick it on the
checklist for next time.


git-svn-id: svn://svn.tartarus.org/sgt/putty@7169 cda61777-01e9-0310-a592-d414129be87e
---

diff --git a/CHECKLST.txt b/CHECKLST.txt
index 6e775f9a..efca86d9 100644
--- a/CHECKLST.txt
+++ b/CHECKLST.txt
@@ -53,6 +53,11 @@ Before tagging a release
    containing the word XXX-REVIEW-BEFORE-RELEASE.
    (Any such comments should state clearly what needs to be done.)
 
+ - Also, do some testing of the Windows version with Minefield, and
+   of the Unix version with valgrind or efence or both. In
+   particular, any headline features for the release should get a
+   workout with memory checking enabled!
+
 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
 system on the compiler command line, and the _only_ place version