and add release to the revision history at the front (release notes
will be pulled in automatically)
+ - get a Google Maps API key and install it in
+ ~/altusmetrumllc/google-maps-api-key. If you don't have a
+ key, the app will still work, but downloading map tiles will
+ be slow, and you will only be able to download a limited
+ number per day.
+
- update the version in configure.ac
git log > ChangeLog
git commit -a
- if this is a -1 release, then
git-buildpackage --git-no-pristine-tar --git-submodules \
- --git-upstream-branch=branch-<version>
+ --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>
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/telemega-v1.0/*.elf \
+ src/telemetrum-v2.0/*.elf \
+ ~/altusmetrumllc/Binaries/
+ cp src/easymini-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 commit -a)
+
- copy the relevant release notes file from doc/ to
/home/bdale/web/altusmetrum/AltOS/releases/<rev>
this pushes fresh documents to the web site
sudo debian/rules clean
- git push origin master branch-<version> debian
+ git push origin master branch-<version> debian pristine-tar
git push --tags
push commits and leave the build tree in an uncluttered state