Expanded allowed text in mhical parse error message.

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index fb7ad979508c81540d6c15d75bad10c76797a56d..b7b99397d1aa3ab4e75e65ed098e7cfd0a681e78 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -1,4 +1,3 @@
-#
 # README.developers
 #
 
@@ -19,13 +18,9 @@ commit checklist
 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?
-
-A buildbot at http://orthanc.ca:8010/waterfall polls for new commits and
-builds them on a few platforms.  Keep an eye on its progress in case
-you've committed something non-portable.  (If you can provide another
-platform, contact the nmh-workers list.)
+7. be sure that commit message starts with one-line synopsis, then a blank line
+8. update/close bug report (with commit id)?
+9. notify nmh-users?
 
 
 ---------------------------------
@@ -315,3 +310,19 @@ here; the convention for release candidates is to use something like
     it assumes that we tag with nmh-x_x-release from now on]:
 
         http://git.savannah.gnu.org/cgit/nmh.git/diff/?h=nmh-1_5-release?h=nmh-1_4-release
+
+
+---------------
+after a release
+---------------
+
+Keep an eye on Debian's packaging, especially what patches they have to
+apply, and the results of their Lintian checker, which even includes
+spelling errors in man pages and binaries.
+
+    https://sources.debian.net/src/nmh/1.6-16/debian/patches/
+    https://lintian.debian.org/full/az@debian.org.html#nmh
+
+Perhaps some nmh developer that uses Debian, or Ubuntu?, could provide
+package-building commands, including lintian(1), for Makefile.am so
+Lintian's complaints are known before release.