1 cheat sheet for making a (stable) release tarball.
3 0. check if your name settings in .hgrc are correct. (have
4 your real name and email address in there).
8 $ git clone git://olsr.org/olsrd.git
9 $ git checkout --track -b stable origin/stable
11 2. check if the DEBUG settings in Makefile.inc are correct:
14 NO_DEBUG_MESSAGES ?= 0
16 now check if it builds correct:
18 $ make uberclean build_all
20 3. Update the changelog
22 4. Change VERS in Makefile.inc to your target release.
23 in this example the target release is 0.5.6-r5
24 Please also write a new version to:
25 gui/win32/Main/Frontend.rc (line 71, around "CAPTION [...]")
26 gui/win32/Inst/installer.nsi (line 57, around "MessageBox MB_YESNO [...]")
28 most likely this is carrying some pre-XXX-release tag.
30 $ grep -E "^VERS" Makefile
39 6. make the release tarball
44 ### creating /tmp/olsrd-0.5.6-r5.tar.gz
45 6c996e94de06115d19dbbcaf6847051a /tmp/olsrd-0.5.6-r5.tar.gz
46 ### creating /tmp/olsrd-0.5.6-r5.tar.bz2
47 e476819be5747758e3d6f579e4096bce /tmp/olsrd-0.5.6-r5.tar.bz2
49 7. check if everything is in the release tarball (ideally on a a
50 different machine) and try to build from the tarball.
52 8. display the used tags:
65 now tag the tree (please stick to the tagging scheme).
67 $ git tag -s OLSRD_0_6_0
71 10. upload the the .tgz and .bz2 tarballs to the http://www.olsr.org/downaload/0.5/
72 section and add a release article on the web.
73 Add a PGP signed textfile with the md5/sha1 sums to the webpage too
75 11. Change VERS in Makefile.inc to your *next* target release.
76 in this example the next target release is pre-0.6.2
78 Please also write a new version to:
79 gui/win32/Main/Frontend.rc (line 71, around "CAPTION [...]")
80 gui/win32/Inst/installer.nsi (line 57, around "MessageBox MB_YESNO [...]")
84 $ grep -E "^VERS" Makefile
93 you are done, congratulations !