X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=Releasing;h=cb92b1e900e323fac0a9477809c0d60aa04b4f5a;hp=a570645a860ab67252902115ca349ce33c9f3a03;hb=dfb9568866ba250a02039cc3429d5ca0603a60d9;hpb=64adfbbb80c90dfe244179d81beaef8a84ed8bd6 diff --git a/Releasing b/Releasing index a570645a..cb92b1e9 100644 --- a/Releasing +++ b/Releasing @@ -1,3 +1,12 @@ +Adding a product to the release + + Make sure the firmware and loader get built by default in + src/Makefile + + Add the firmware to altosui/Makefile.am + + Add the firmware to altosui/altos-windows.nsi.in + These are Bdale's notes on how to do a release. - make sure build environment is up to date @@ -8,6 +17,7 @@ These are Bdale's notes on how to do a release. - 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 + (cd ~/altusmetrumllc; git pull) 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 @@ -21,10 +31,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 - - 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,7 +50,7 @@ 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: - gbp dch --release --new-version=-1 --multimaint-merge + gbp dch --release --multimaint-merge --new-version=-1 git commit -n debian/changelog -m "update changelog for Debian build" @@ -68,26 +78,36 @@ 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/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/telemetrum-v2.0/*.elf \ + cp src/chaoskey-v1.0/{*.elf,*.ihx} \ + src/easymega-v1.0/{*.elf,*.ihx} \ + src/easymini-v1.0/{*.elf,*.ihx} \ + src/easymini-v2.0/{*.elf,*.ihx} \ + src/telebt-v3.0/{*.elf,*.ihx} \ + src/telebt-v4.0/{*.elf,*.ihx} \ + src/teledongle-v3.0/{*.elf,*.ihx} \ + src/telegps-v1.0/{*.elf,*.ihx} \ + src/telemega-v1.0/{*.elf,*.ihx} \ + src/telemega-v2.0/{*.elf,*.ihx} \ + src/telemetrum-v2.0/{*.elf,*.ihx} \ + src/telemini-v3.0/{*.elf,*.ihx} \ ~/altusmetrumllc/Binaries/ - cp src/easymega-v1.0/flash-loader/*.elf \ + cp src/chaoskey-v1.0/flash-loader/{*.elf,*.bin} \ + src/easymega-v1.0/flash-loader/*.elf \ src/easymini-v1.0/flash-loader/*.elf \ + src/easymini-v2.0/flash-loader/{*.elf,*.bin} \ src/telebt-v3.0/flash-loader/*.elf \ + src/telebt-v4.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 \ + src/telemini-v3.0/flash-loader/{*.elf,*.bin} \ ~/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)