X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=Releasing;h=d95339b51a2e333ff043c496e4d7a919e9fec30e;hp=c5ecdf3473a30e5a24a787ad63ba1f54766b6706;hb=04759dddeb29e4de9f7e6b3673dc06c633fa2369;hpb=75db560e2c9fbb2889db507acc93e889bf15bc2a diff --git a/Releasing b/Releasing index c5ecdf34..d95339b5 100644 --- a/Releasing +++ b/Releasing @@ -5,6 +5,8 @@ These are Bdale's notes on how to do a release. git checkout master + - update the version in configure.ac if Keith hasn't already + - 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 \ @@ -19,12 +21,10 @@ These are Bdale's notes on how to do a release. 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 sure there is a doc/release-notes-.inc + - make sure that doc/altusmetrum-docinfo.xml 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" @@ -40,19 +40,19 @@ These are Bdale's notes on how to do a release. - 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 + gbp 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 \ + gbp 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 + gbp buildpackage --git-submodules git tag debian/ @@ -61,32 +61,44 @@ These are Bdale's notes on how to do a release. make distclean - ./autogen.sh --with-fat-dir=/home/bdale/web/altusmetrum/AltOS/releases + ./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/easymini-v1.0/*.elf \ + cp src/easymega-v1.0/*.elf \ + src/easymini-v1.0/*.elf \ + src/telebt-v3.0/*.elf \ + src/teledongle-v3.0/*.elf \ src/telegps-v1.0/*.elf \ src/telemega-v1.0/*.elf \ + src/telemega-v2.0/*.elf \ src/telemetrum-v2.0/*.elf \ ~/altusmetrumllc/Binaries/ - cp src/easymini-v1.0/flash-loader/*.elf \ + cp src/easymega-v1.0/flash-loader/*.elf \ + src/easymini-v1.0/flash-loader/*.elf \ + src/telebt-v3.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/telemega-v2.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 + - copy the relevant release notes .html file from doc/ to /home/bdale/web/altusmetrum/AltOS/releases/ + (cd ~/web/altusmetrum/AltOS/releases/ ; rm *.tar.bz2) + - 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 MicroPeak installers from AltOS/releases to there + 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