+To make a public release of mmh (we'll use version 1.0 as example
+here):
+
+ 1. % echo 1.0 > VERSION
+ % date +"%Y-%m-%d" > DATE
+ (DATE should contain something like "2012-12-08")
+
+ 2. % git commit VERSION DATE; git push
+
+ 3. % git tag -a mmh-1.0 -m 'Releasing mmh-1.0'
+
+ 4. % make mmhdist
+
+ 5. Untar mmh-1.0.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 mmh-1.0
+ % tar cvf - mmh-1.0 | gzip -c > mmh-1.0.tar.gz
+
+ 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 mmh is
+ being installed, making it possible for that user to Trojan the mmh
+ 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 mmh from it.
+
+ 8. If all is well and your tarball is final, go back to your workspace
+ and do:
+
+ % echo 1.0+dev > VERSION
+
+ 9. % git commit VERSION; git push
+
+10. Generate an MD5 hash and a PGP signature of the tarball: