1 These are Bdale's notes on how to do a release.
3 confirm that doc/ has a release-notes file for the new release
4 - add a release notes file
6 - link release notes in doc/altusmetrum.xsl
8 update the version in configure.ac and commit
12 - make sure checked-out tree is "clean" so git won't complain
16 at this point, we have Debian packages
18 git tag debian/<version>
22 ./autogen.sh --with-fat-dir=/home/bdale/web/altusmetrum/AltOS/releases
25 this pushes packages for each platform to web site
27 - copy the relevant release notes file from doc/ to
28 /home/bdale/web/altusmetrum/AltOS/releases/<rev>
30 - go edit ~/web/altusmetrum/AltOS/releases/<rev>.mdwn to include
31 release date and explicit ref to dir contents so the AltOS page
32 shows versioned links, commit and push
34 (cd doc ; make publish)
36 this pushes fresh documents to the web site
38 sudo debian/rules clean
42 push commits and leave the build tree in an uncluttered state
44 Testing before a release
46 To verify that a build works, the following need to be checked
51 2) Connect TM *and* TD devices. Verify that you can Monitor
52 Flight from the TD and Configure Telemetrum from the TM.
54 3) Replay Flight, using your favorite .eeprom file. Check
55 each tab, especially the 'Site Map' tab. Make sure the
58 4) Graph Data. Graph a favorite .eeprom file. Make sure you
59 can zoom in on some region of the graph.