X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=Releasing;h=fd5227978b4f821cc828ec64e2180a90bd1b83ef;hp=a1c510fdbabbdecf94c03560403ca261cfb4a969;hb=d1af180c2d2a2caf1e13f00d83f2b86ba26de27f;hpb=505c6a1f8b8d68fe6f74dcb4428c860157fae3de

diff --git a/Releasing b/Releasing
index a1c510fd..fd522797 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,8 +21,6 @@ These are Bdale's notes on how to do a release.
 		git checkout branch-<version>		# 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-<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
@@ -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=<version>-1 --multimaint-merge
+	gbp dch --release --new-version=<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-<version> \ # eg 1.3
 			--git-upstream-tag=<version>	         # eg 1.3.1
 		pristine-tar commit \
 			../build-area/altos_<version>.orig.tar.gz \
 			branch-<version>
 	  else if this is not a -1 release
-		git-buildpackage --git-submodules
+		gbp buildpackage --git-submodules
 
 	git tag debian/<version>
 
@@ -61,20 +61,29 @@ 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) 
@@ -83,11 +92,13 @@ These are Bdale's notes on how to do a release.
 	- copy the relevant release notes file from doc/ to 
 	    /home/bdale/web/altusmetrum/AltOS/releases/<rev>
 
+	(cd ~/web/altusmetrum/AltOS/releases/<rev> ; rm *.tar.bz2)
+
 	- create /home/bdale/web/altusmetrum/MicroPeak/releases/<rev>,
 	  and move the MicroPeak installers from AltOS/releases to there
 		
 	- create /home/bdale/web/altusmetrum/TeleGPS/releases/<rev>,
-	  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/<rev>.mdwn, 
 	  /home/bdale/web/altusmetrum/MicroPeak/releases/<rev>.mdwn, and