blob: 4e76d791887235ddb2ca095ab7e65b7c95936ed1 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
These are Bdale's notes on how to do a release.
- make sure there's a suitable ARM Cortex toolchain in /opt/cortex!
git checkout master
- 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)
- update the version in configure.ac
- make absolutely sure checked-out tree is "clean" (commit as needed)
- if this is an x.y release, then:
git checkout -b branch-<version>
- if this is an x.y.z release, then:
git checkout branch-<version> # the x.y parts only
git merge master
git log > ChangeLog
git commit -a
git tag -a <version>
git checkout debian
git merge branch-<version>
- edit .git/gbp.conf to use branch-<version> as upstream and debian
as packaging branch, if needed
- 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
git commit -n debian/changelog -m "update changelog for Debian build"
- if this is a -1 release, then
git-buildpackage --git-no-pristine-tar
pristine-tar commit \
../build-area/altos/altos_<version>.orig.tar.gz \
branch-<version>
else if this is not a -1 release
git-buildpackage
git tag debian/<version>
- at this point we have packages in ~/debian/build-area/altos, now
we move on to the non-Debian part of the release process
make distclean
./autogen.sh --with-fat-dir=/home/bdale/web/altusmetrum/AltOS/releases
make && make fat
this pushes packages for each platform to web site
- copy the relevant release notes file from doc/ to
/home/bdale/web/altusmetrum/AltOS/releases/<rev>
- go edit ~/web/altusmetrum/AltOS/releases/<rev>.mdwn to include
release date and explicit ref to dir contents so the AltOS page
shows versioned links, commit and push
(cd doc ; make publish)
this pushes fresh documents to the web site
sudo debian/rules clean
git push origin master branch-1.1 debian
git push --tags
push commits and leave the build tree in an uncluttered state
Testing before a release
To verify that a build works, the following need to be checked
on each platform:
1) Install package
2) Connect TM *and* TD devices. Verify that you can Monitor
Flight from the TD and Configure Telemetrum from the TM.
3) Replay Flight, using your favorite .eeprom file. Check
each tab, especially the 'Site Map' tab. Make sure the
sound works.
4) Graph Data. Graph a favorite .eeprom file. Make sure you
can zoom in on some region of the graph.
|
