diff options
| author | Bdale Garbee <bdale@gag.com> | 2013-05-16 01:53:42 -0600 | 
|---|---|---|
| committer | Bdale Garbee <bdale@gag.com> | 2013-05-16 01:53:42 -0600 | 
| commit | 7b4e5943c4d8da20e6bfcc6517749108e88aa7a5 (patch) | |
| tree | 9c0ead075e23f81f8b202e0d69e21644fc03131f | |
| parent | b78cf1614a1cd991799226c8d3d6792fc2083dfc (diff) | |
update Releasing document to reflect process as of 1.2
| -rw-r--r-- | Releasing | 14 | 
1 files changed, 8 insertions, 6 deletions
| @@ -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 | 
