aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Bremner <bremner@debian.org>2011-11-16 07:25:57 -0400
committerDavid Bremner <bremner@debian.org>2011-11-16 07:25:57 -0400
commitb2d9e716e78aa8ec595493da1cde004e71bbea76 (patch)
tree8d3851efcab615b09bdf5b919140f900091a733f
parentd78d5b62585bdfb6c21123b513aa70f1a66efb80 (diff)
RELEASING: update discussion of version handling
This is definitely reaching the point where it should be automated.
-rw-r--r--RELEASING6
1 files changed, 5 insertions, 1 deletions
diff --git a/RELEASING b/RELEASING
index 5816ec9..2cec380 100644
--- 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