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. man page and other documentation updated?
+4. docs/pending-release-notes updated?
+5. should commit message reference bug report?
+6. update/close bug report (with commit id)?
+7. notify nmh-users?
-------------------------
releasing nmh
-------------
-To make a public release of nmh (we'll use version 1.5 and my mhost.com
-account, danh, as examples here; the convention for release candidates
-is to use something like "1.5-RC1"):
+To make a public release of nmh (we'll use version 1.5 as the example
+here; the convention for release candidates is to use something like
+"1.5-RC1"):
1. % echo 1.5 > VERSION
% date +"%e %B %Y" > DATE
5. If all is well and your tarball is final, go back to your workspace and do:
- % echo 1.0.4+dev > VERSION
+ % echo 1.5+dev > VERSION
6. % git commit VERSION; git push
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