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- - if this is an x.y.z release, then: git checkout branch- # 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-.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 # full x.y.z version - make sure .git/gbp.conf set to use branch- as upstream git checkout debian git merge branch- - verify debian/changelog is "clean" ending in last release version - craft a suitable debian/changelog entry, possibly using: git-dch --release --new-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- \ # eg 1.3 --git-upstream-tag= # eg 1.3.1 pristine-tar commit \ ../build-area/altos_.orig.tar.gz \ branch- else if this is not a -1 release git-buildpackage --git-submodules git tag debian/ - at this point we have packages in ~/debian/build-area/altos, now we move on to the non-Debian part of the release process make distclean ./autogen.sh --enable-multi-arch \ --with-fat-dir=/home/bdale/web/altusmetrum/AltOS/releases make && make fat this pushes packages for each platform to web site # store a stable copy of ARM binaries for production use cp src/easymega-v1.0/*.elf \ src/easymini-v1.0/*.elf \ src/teledongle-v3.0/*.elf \ src/telegps-v1.0/*.elf \ src/telemega-v1.0/*.elf \ src/telemetrum-v2.0/*.elf \ ~/altusmetrumllc/Binaries/ cp src/easymega-v1.0/flash-loader/*.elf \ src/easymini-v1.0/flash-loader/*.elf \ src/teledongle-v3.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/ - create /home/bdale/web/altusmetrum/MicroPeak/releases/, and move the MicroPeak installers from AltOS/releases to there - create /home/bdale/web/altusmetrum/TeleGPS/releases/, and move the TeleGPS installers from AltOS/releases to there - go edit ~/web/altusmetrum/AltOS/releases/.mdwn, /home/bdale/web/altusmetrum/MicroPeak/releases/.mdwn, and /home/bdale/web/altusmetrum/TeleGPS/releases/.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- debian pristine-tar git push --tags push commits and leave the build tree in an uncluttered state Testing before a release To verify that a build works, the following need to be checked on each platform: 1) Install package 2) Connect TM *and* TD devices. Verify that you can Monitor Flight from the TD and Configure Telemetrum from the TM. 3) Replay Flight, using your favorite .eeprom file. Check each tab, especially the 'Site Map' tab. Make sure the sound works. 4) Graph Data. Graph a favorite .eeprom file. Make sure you can zoom in on some region of the graph.