X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/2e04b8ea0e57e411665aa6a8814ff65db0d4cd2b..0813132987677a8b0cf3b4d0e8bf851657deeadd:/docs/README.developers?ds=sidebyside diff --git a/docs/README.developers b/docs/README.developers index f0f05c82..b7b99397 100644 --- a/docs/README.developers +++ b/docs/README.developers @@ -1,4 +1,3 @@ -# # README.developers # @@ -8,6 +7,7 @@ local info best encoded in a comment) are encouraged to share their wisdom here. Following a commit checklist, the topics are organized alphabetically. + ---------------- commit checklist ---------------- @@ -18,13 +18,15 @@ 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? +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? --------------------------------- 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). @@ -308,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.