X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/a4999fa48c92214848cc5d792d1d6a35e3a189bb..a6cae3aa524fd8517f50bd6a7602d06faa669632:/docs/README.developers?ds=sidebyside

diff --git a/docs/README.developers b/docs/README.developers
index b342d1b2..f99d1080 100644
--- 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
@@ -185,7 +198,6 @@ here; the convention for release candidates is to use something like
      exmh-users@redhat.com
      exmh-workers@redhat.com
      mh-e-users@lists.sourceforge.net
-     mh-users@ics.uci.edu *or* comp.mail.mh (there is a bidirectional gateway)
 
     If the release fixes significant security holes, also send an announcement
     to bugtraq@securityfocus.com.  The exmh lists require you to be subscribed