[PATCH 3/3] RELEASING: document the semi-automated version propagation.

Subject: [PATCH 3/3] RELEASING: document the semi-automated version propagation.

Date: Thu, 17 Nov 2011 22:26:26 -0400

To: notmuch@notmuchmail.org

Cc: David Bremner

From: David Bremner

From: David Bremner <bremner@debian.org>

The instructions are purposely a bit coy about what files are updated,
so we don't have to update immediately when something else is plugged
into the make recipe.
---
 RELEASING |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/RELEASING b/RELEASING
index e3e0cef..88dab04 100644
--- a/RELEASING
+++ b/RELEASING
@@ -62,11 +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.
 
-	Update bindings/python/notmuch/version.py to match version.
+	When you are happy with the file 'version', run
 
-	Update the version in notmuch.1 to match version.
+	     make update-versions
 
-	XXX: Probably these last two steps should be (semi-)automated.
+	to propagate the version to the other places needed.
 
 	Commit these changes.
 
-- 
1.7.7.1

Thread: