ReleaseChecklist

(originally written by Paul Jakma for the old Quagga wiki)

Table of Contents Get a good release together, and queue it up in git When happy, push out the release Generate changelogs Sign release tarball Upload the files

Get a good release together, and queue it up in git

git checkout RE-stable-0.99
edit configure.ac, bump the release number
do a make dist, ensure it produces a quagga-<newrelease>.tar.gz (if this is a fresh cloned repository, ./update-autotools && ./configure will do necessary initialization)
build test this new tarball (even if you've already tested the Quagga sources to your satisfication, preferably on multiple OSes): ./configure && make all
save local working copy: git add configure.ac && git commit

...to the canonical quagga.git tree (below presumes your local git HEAD is the release)

tag it:
```
git tag quagga_<version>_release
```
ideally you'll have set up your git config with appropriate shorthand aliases, but otherwise:
```
git push ssh://code.quagga.net/var/git/quagga.git HEAD:master quagga_<version>_release
```
This pushes your local HEAD to the 'master' branch at the given repository, and also pushes out the tag.

the full changelog file:

git log --no-merges quagga_0_99_11_release..quagga_0_99_12_release > quagga-0.99.12.changelog.txt

the subject lines, suitable for use as a summary in the release announcement to quagga-users and the website:

git log --no-merges --pretty=short quagga_0_99_11_release..quagga_0_99_12_release | egrep -v '^(commit|short|Author|$)'

Create a detached, ASCII, PGP signature using the maintainers key:

gpg -ab -u maintainers@quagga.net quagga-<ver>.tar.gz

You should now have 3 files, e.g.:

$ ls quagga-0.99.12*
quagga-0.99.12.changelog.txt quagga-0.99.12.tar.gz quagga-0.99.12.tar.gz.asc