RELEASING: update discussion of version handling

This is definitely reaching the point where it should be automated.

diff --git a/RELEASING b/RELEASING
index 5816ec97009dc27e6e1d781e2f79fc1cd35427bc..2cec3807dfaf80708992f3abac349baf197bdfd9 100644 (file)
--- a/RELEASING
+++ b/RELEASING
@@ -62,7 +62,11 @@ repository. From here, there are just a few steps to release:
        be "1.0.1" and a subsequent bug-fix release would be "1.0.2"
        etc.
 
-       Commit this change.
+       Update bindings/python/notmuch/version.py to match version.
+
+       Update the version in notmuch.1 to match version.
+
+       Commit these changes.
 
 5) Create an entry for the new release in debian/changelog