update release process docs

[fw/altos] / Releasing

diff --git a/Releasing b/Releasing
index a7263c6162306541a206cf620037911c5037ffe4..80d39f6a951965bb0606b1d2891ddd4d1ea314e8 100644 (file)
--- a/Releasing
+++ b/Releasing
@@ -4,10 +4,9 @@ These are Bdale's notes on how to do a release.
 
        git tag -a <version>
 
-       git-buildpackage --git-ignore-new
+       - make sure checked-out tree is "clean" so git won't complain
 
-               use --git-ignore-new so trash in checked-out tree doesn't
-               cause the build to fail!
+       git-buildpackage
 
                at this point, we have Debian packages
 
@@ -18,6 +17,9 @@ These are Bdale's notes on how to do a release.
 
                this pushes packages for each platform to web site
 
+       - 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
@@ -25,3 +27,24 @@ These are Bdale's notes on how to do a release.
        (cd doc ; make publish)
 
                this pushes fresh documents to the web site
+
+       sudo debian/rules clean
+
+               leave the build tree in an unclutterd 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.