summaryrefslogtreecommitdiff
path: root/Releasing
diff options
context:
space:
mode:
authorBdale Garbee <bdale@gag.com>2016-07-05 10:23:18 +0200
committerBdale Garbee <bdale@gag.com>2016-07-05 10:23:18 +0200
commit148b013dd29c26920ddfb53449ed4d8cc5a4b5ee (patch)
treee4845fa02606e4f209d485f155b7278f84d33428 /Releasing
parentea1ff225f1f450ee3fc377807d1bb7b982bf792d (diff)
parentcd97128e30c47edfcc71f7d872cbdad14867934c (diff)
Merge branch 'master' into branch-1.6
Diffstat (limited to 'Releasing')
-rw-r--r--Releasing3
1 files changed, 2 insertions, 1 deletions
diff --git a/Releasing b/Releasing
index d95339b5..7a87a48b 100644
--- a/Releasing
+++ b/Releasing
@@ -8,6 +8,7 @@ These are Bdale's notes on how to do a release.
- update the version in configure.ac if Keith hasn't already
- make sure the Google Maps API key is in the build chroot and root
+ (cd ~/altusmetrumllc; git pull)
sudo mkdir -p /var/cache/pbuilder/base.cow/opt/google /opt/google
sudo cp ~/altusmetrumllc/google-maps-api-key \
/var/cache/pbuilder/base.cow/opt/google/maps-api-key
@@ -40,7 +41,7 @@ These are Bdale's notes on how to do a release.
- verify debian/changelog is "clean" ending in last release version
- craft a suitable debian/changelog entry, possibly using:
- gbp dch --release --new-version=<version>-1 --multimaint-merge
+ gbp dch --release --multimaint-merge --new-version=<version>-1
git commit -n debian/changelog -m "update changelog for Debian build"