X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=Releasing;h=a1c510fdbabbdecf94c03560403ca261cfb4a969;hp=8b30600771f7fddd686ae5d3a56052be58b59b5e;hb=0fd867f504dd7df62e95da98ded511bb7b9e4c66;hpb=02e657e45e217dc483a81f28020cfe65a826e9be diff --git a/Releasing b/Releasing index 8b306007..a1c510fd 100644 --- a/Releasing +++ b/Releasing @@ -1,35 +1,39 @@ 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 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 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 - - 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. + - 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 - git log > ChangeLog - git commit -a + - 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" - - if this is an x.y release, then: - git checkout -b branch- - git tag -a - - edit .git/gbp.conf to use branch- as upstream + git log > ChangeLog + git commit -a + git tag -a # full x.y.z version - - if this is an x.y.z release, then: - git checkout branch- # the x.y parts only - git merge master - 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- @@ -64,14 +68,17 @@ These are Bdale's notes on how to do a release. # 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 commit -a) + (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/ @@ -79,10 +86,14 @@ These are Bdale's notes on how to do a release. - create /home/bdale/web/altusmetrum/MicroPeak/releases/, and move the MicroPeak installers from AltOS/releases to there - - go edit ~/web/altusmetrum/AltOS/releases/.mdwn and - /home/bdale/web/altusmetrum/MicroPeak/releases/.mdwn, to - include release date and explicit ref to dir contents so the - web pages shows versioned links, commit and push + - create /home/bdale/web/altusmetrum/TeleGPS/releases/, + and move the MicroPeak 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)