These are Bdale's notes on how to do a release.
+ - make sure build environment is up to date
+ sudo cowbuilder --update
+
git checkout master
+ - make sure the Google Maps API key is in the build chroot and root
+ 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
+ sudo ln -sf /home/bdale/altusmetrumllc/google-maps-api-key \
+ /opt/google/maps-api-key
+
+ - if this is an x.y release, then:
+ git checkout -b branch-<version>
+
+ - 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"
- - update the version in configure.ac
git log > ChangeLog
git commit -a
- - make absolutely sure checked-out tree is "clean"
- - 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
+ git tag -a <version> # full x.y.z version
- - edit .git/gbp.conf to use branch-<version> as upstream if needed
+ - make sure .git/gbp.conf set to use branch-<version> as upstream
git checkout debian
git merge branch-<version>
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-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/altos_<version>.orig.tar.gz \
+ ../build-area/altos_<version>.orig.tar.gz \
branch-<version>
else if this is not a -1 release
- git-buildpackage
+ git-buildpackage --git-submodules
git tag debian/<version>
this pushes packages for each platform to web site
+ # store a stable copy of ARM binaries for production use
+ cp src/easymini-v1.0/*.elf \
+ src/telegps-v1.0/*.elf \
+ src/telemega-v1.0/*.elf \
+ src/telemetrum-v2.0/*.elf \
+ ~/altusmetrumllc/Binaries/
+ cp src/easymini-v1.0/flash-loader/*.elf \
+ src/telegps-v1.0/flash-loader/*.elf \
+ src/telemega-v1.0/flash-loader/*.elf \
+ src/telemetrum-v2.0/flash-loader/*.elf \
+ ~/altusmetrumllc/Binaries/loaders/
+ (cd ~/altusmetrumllc ; git add Binaries ; git commit -a)
+ (cd ~/altusmetrumllc ; git push)
+
- copy the relevant release notes file from doc/ to
/home/bdale/web/altusmetrum/AltOS/releases/<rev>
- - go edit ~/web/altusmetrum/AltOS/releases/<rev>.mdwn to include
- release date and explicit ref to dir contents so the AltOS page
- shows versioned links, commit and push
+ - create /home/bdale/web/altusmetrum/MicroPeak/releases/<rev>,
+ and move the MicroPeak installers from AltOS/releases to there
+
+ - create /home/bdale/web/altusmetrum/TeleGPS/releases/<rev>,
+ and move the MicroPeak installers from AltOS/releases to there
+
+ - go edit ~/web/altusmetrum/AltOS/releases/<rev>.mdwn,
+ /home/bdale/web/altusmetrum/MicroPeak/releases/<rev>.mdwn, and
+ /home/bdale/web/altusmetrum/TeleGPS/releases/<rev>.mdwn
+
+ - make sure the Windows stuff is like 1-4-1, not 1.4.1!
(cd doc ; make publish)
this pushes fresh documents to the web site
sudo debian/rules clean
- git push origin master branch-1.1 debian
+ git push origin master branch-<version> debian pristine-tar
git push --tags
push commits and leave the build tree in an uncluttered state
projects / fw / altos / blobdiff