More homing in on the test-pick warning. Also, removed

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index bae6d9ccffdba678201574c932c5d922ba1db4c7..f99d10801a4e9f6411414174c41d13fe93b5f72d 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -6,7 +6,20 @@ This file is intended to provide a few tips for anyone doing development on nmh.
 Developers who learn things "the hard way" about the nmh codebase (as opposed to
 local info best encoded in a comment) are encouraged to share their wisdom here.
 
-The topics are organized alphabetically.
+Following a commit checklist, the topics are organized alphabetically.
+
+----------------
+commit checklist
+----------------
+
+1. code updated?
+2. test added?
+3. make distcheck passed?
+4. man page and other documentation updated?
+5. docs/pending-release-notes updated?
+6. should commit message reference bug report?
+7. update/close bug report (with commit id)?
+8. notify nmh-users?
 
 
 -------------------------
@@ -18,7 +31,7 @@ or other related files, you'll need to first install GNU m4, available
 from <ftp://ftp.gnu.org/pub/gnu/m4/>, then GNU autoconf
 (<ftp://ftp.gnu.org/pub/gnu/autoconf/>) and GNU automake
 (<ftp://ftp.gnu.org/pub/gnu/automake/>).  Nmh is currently using a
-minimum of autoconf 2.61 and automake 1.10.
+minimum of autoconf 2.68 and automake 1.12.
 
 Most of the configure-related files are automatically generated.
 The only files you should need to manually edit are configure.ac