Document the release procedure.

diff --git a/RELEASE-PROCEDURE b/RELEASE-PROCEDURE
new file mode 100644 (file)
index 0000000..d63a8b1
--- /dev/null
+++ b/RELEASE-PROCEDURE
@@ -0,0 +1,27 @@
+HOW TO RELEASE FILE
+
+@(#) $File: RELEASE-PROCEDURE,v 1.1 2014/03/16 08:53:09 kim Exp $
+
+**DRAFT** added 2014-03-16
+
+1)  Update version number in configure.ac
+2)  Note the new version in ChangeLog
+3)  Update README if applicable
+4)  Commit changes into CVS
+5)  Rebuild and run tests (see README.DEVELOPER)
+6)  Tag the release with FILEx_yy
+7)  Create the source tarball: make dist
+8)  Make the source tarball available on ftp
+9)  Add the new version to bugs.gw.com:
+    - Click: Manage > Manage Projects > file
+    - Scroll down to "Versions"
+    - Click on "Edit" next to the HEAD version
+    - Change the "Version" from HEAD to the newly released version
+    - Change the "Date Order" to the current time
+    - Check the "Released" box
+    - Click on "Update Version"
+    - Type HEAD into the box at the bottom of the version list and
+      click on "Add and Edit Version"
+    - Set the "Date Order" to 2030-01-01 (i.e. far in the future)
+    - Click on "Update Version"
+10) Mail an announcement to file@mx.gw.com