+account, danh, as examples here; the convention for release candidates
+is to use something like "1.0.4-RC1"):
+
+ 1. % echo 1.0.4 > VERSION
+ % date +"%e %B %Y" > DATE
+ (DATE should contain something like "30 December 2000")
+
+ 2. % git commit VERSION DATE; git push
+
+ 3. % git tag -a nmh-1_0_4 -m 'Releasing nmh-1_0_4.'
+
+ 4. % make nmhdist
+
+ 5. Untar nmh-1.0.4.tar.gz and `diff -r' it vs. your workspace. Make
+ sure no files got left out of the distribution that should be in it
+ (due to someone forgetting to update the DIST variables in the
+ Makefiles).
+
+ 6. If you have root access on your machine, it's good at this point to do:
+
+ % chown -R 0:0 nmh-1.0.4
+ % tar cvf nmh-1.0.4.tar nmh-1.0.4
+ % gzip nmh-1.0.4.tar
+
+ If you leave the files in the archive as being owned by yourself, your UID
+ may coincide with one of a user on a machine where nmh is being installed,
+ making it possible for that user to Trojan the nmh code before the system
+ administrator finishes installing it.
+
+ 7. Make sure your new tarball uncompresses and untars with no problem. Make
+ sure you can configure, make, and install nmh from it.
+
+ 8. If all is well and your tarball is final, go back to your workspace and do:
+
+ % echo 1.0.4+dev > VERSION
+
+ 9. % git commit VERSION; git push