blob: 98290576797b1acff01866e0577e6d21f3ee1242 (
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
|
These are Bdale's notes on how to do a release.
confirm that doc/ has a release-notes file for the new release
- add a release notes file
- update doc/Makefile
- link release notes in doc/altusmetrum.xsl
update the version in configure.ac and commit
git tag -a <version>
- make sure checked-out tree is "clean" so git won't complain
git-buildpackage
at this point, we have Debian packages
git tag debian/<version>
make distclean
./autogen.sh --with-fat-dir=/home/bdale/web/altusmetrum/AltOS/releases
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
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.
|
