document release process

diff --git a/DEVELOPING b/DEVELOPING
index 5f15e1590a481ebf7f5548a449facc96270f5546..5dfd9b771faf3c17655dfa348bb80f72baf63849 100644 (file)
--- a/DEVELOPING
+++ b/DEVELOPING
@@ -160,3 +160,28 @@ The NO example just imports a set of functions from the output module.  It is
 somewhat annoying because the import line needs to be modified when functions
 are needed and often unused functions are left in the import line until someone
 comes along with a linter to clean up (does not happen often).
+
+Releases
+--------
+
+First create a git tag for this release:
+       git tag v2.2.8
+
+Then create the tarball:
+       ./mkrelease.sh --changelog-rev v2.2.7 --tag 2.2.8
+
+Unpack the tarball and run tests:
+       ./runtests.sh
+Make sure you have all supported python versions installed:
+       2.6 2.7 3.2 3.3
+
+Version bump the ebuild and verify it can re-install itself:
+       emerge portage
+       emerge portage
+
+Publish the results (no going back now):
+       - Push the new git tag
+       - Upload the tarball
+       - Commit the new ebuild version
+
+Close the bugs blocking the tracker bug for this release.