From 7b4e5943c4d8da20e6bfcc6517749108e88aa7a5 Mon Sep 17 00:00:00 2001
From: Bdale Garbee <bdale@gag.com>
Date: Thu, 16 May 2013 01:53:42 -0600
Subject: [PATCH] update Releasing document to reflect process as of 1.2

---
 Releasing | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/Releasing b/Releasing
index ce4df7c2..4e76d791 100644
--- a/Releasing
+++ b/Releasing
@@ -10,22 +10,24 @@ These are Bdale's notes on how to do a release.
 	  will be pulled in automatically)
 
 	- update the version in configure.ac
-        git log > ChangeLog
-	git commit -a
-	- make absolutely sure checked-out tree is "clean" 
+	- make absolutely sure checked-out tree is "clean" (commit as needed)
 	- if this is an x.y release, then:
 		git checkout -b branch-<version>
-		git tag -a <version>
 	- if this is an x.y.z release, then:
 		git checkout branch-<version>		# the x.y parts only
 		git merge master
-		git tag -a <version>			# full x.y.z version
 
-	- edit .git/gbp.conf to use branch-<version> as upstream if needed
+        git log > ChangeLog
+	git commit -a
+
+	git tag -a <version>
 
 	git checkout debian
 	git merge branch-<version>
 
+	- edit .git/gbp.conf to use branch-<version> as upstream and debian
+	  as packaging branch, if needed
+
 	- verify debian/changelog is "clean" ending in last release version
 	- craft a suitable debian/changelog entry, possibly using:
 	git-dch --release --new-version=<version>-1 --multimaint-merge
-- 
2.30.2