+ - if this is an x.y.z release, then:
+ git checkout branch-<version> # the x.y parts only
+ - cherry-pick or merge appropriate content from master
+
+ - update the version in configure.ac
+
+ - make sure there is a doc/release-notes-<version>.xsl
+ - make sure that doc/altusmetrum.xsl has the right copyright year,
+ and add release to the revision history at the front (release notes
+ will be pulled in automatically)
+ - make absolutely sure checked-out tree is "clean"
+ - make absolutely sure the pdclib/ submodule is on the master branch,
+ up to date, and "clean"
+
+ git log > ChangeLog
+ git commit -a
+ git tag -a <version> # full x.y.z version
+
+ - make sure .git/gbp.conf set to use branch-<version> as upstream
+
+ git checkout debian
+ git merge branch-<version>
+
+ - 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
+
+ git commit -n debian/changelog -m "update changelog for Debian build"
+
+ - if this is a -1 release, then
+ git-buildpackage --git-no-pristine-tar --git-submodules \
+ --git-upstream-branch=branch-<version> \ # eg 1.3
+ --git-upstream-tag=<version> # eg 1.3.1
+ pristine-tar commit \
+ ../build-area/altos_<version>.orig.tar.gz \
+ branch-<version>
+ else if this is not a -1 release
+ git-buildpackage --git-submodules
+
+ git tag debian/<version>
+
+ - at this point we have packages in ~/debian/build-area/altos, now
+ we move on to the non-Debian part of the release process