-#
# README.developers
#
Following a commit checklist, the topics are organized alphabetically.
+
----------------
commit checklist
----------------
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.)
+
---------------------------------
C library/system call usage notes
---------------------------------
+
* Use m_mktemp2() or m_mktemp() instead of mkstemp(3) (see section on
nmh temporary files below).
* Use m_unlink() instead of unlink(3).
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.