From b2d9e716e78aa8ec595493da1cde004e71bbea76 Mon Sep 17 00:00:00 2001
From: David Bremner <bremner@debian.org>
Date: Wed, 16 Nov 2011 07:25:57 -0400
Subject: [PATCH] RELEASING: update discussion of version handling

This is definitely reaching the point where it should be automated.
---
 RELEASING | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/RELEASING b/RELEASING
index 5816ec97..2cec3807 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
 
-- 
2.45.2