make sure to use Google Maps API key for official builds

[fw/altos] / Releasing

diff --git a/Releasing b/Releasing
index 8627d864da6e107e0f8a8a68a8fff99385182491..d7b337e625fd97aed61e708ed94df9dd0e45abd4 100644 (file)
--- a/Releasing
+++ b/Releasing
@@ -2,11 +2,21 @@ These are Bdale's notes on how to do a release.
 
        git checkout master
 
+       - make sure the Google Maps API key is in the build chroot
+               mkdir -p /var/cache/pbuilder/base.cow/opt/google
+               cp ~/altusmetrumllc/google-maps-api-key \
+                       /var/cache/pbuilder/base.cow/opt/google/maps-api-key
        - 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)
 
+       - 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
@@ -36,7 +46,8 @@ These are Bdale's notes on how to do a release.
 
        - 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>
@@ -55,14 +66,31 @@ These are Bdale's notes on how to do a release.
 
                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) 
+
        - copy the relevant release notes file from doc/ to 
            /home/bdale/web/altusmetrum/AltOS/releases/<rev>
 
        - create /home/bdale/web/altusmetrum/MicroPeak/releases/<rev>,
          and move the MicroPeak installers from AltOS/releases to there
                
-       - go edit ~/web/altusmetrum/AltOS/releases/<rev>.mdwn and 
-         /home/bdale/web/altusmetrum/MicroPeak/releases/<rev>.mdwn, to 
+       - 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, to 
          include release date and explicit ref to dir contents so the 
          web pages shows versioned links, commit and push
 
@@ -71,7 +99,7 @@ These are Bdale's notes on how to do a release.
                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