Developers ========== Making a release ---------------- 1. Bump the version within the `AC_INIT` macro call in `configure.ac`. 2. Update the build system by running: `./autogen.sh`. 3. Build the trivial packages: This all depends on a `gh-pages` branch: git branch gh-pages origin/gh-pages First build the distribution: ./configure make distcheck On any system you can build the tarball, Homebrew package, Arch PKGBUILD, and tag: ./maint/release build tarball rcm-*.tar.gz ./maint/release build homebrew rcm-*.tar.gz ./maint/release build arch rcm-*.tar.gz ./maint/release build tag rcm-*.tar.gz You need mdocml to tranform the manpages into HTML: ./maint/release build man_html rcm-*.tar.gz Once built, you can push it live: ./maint/release push tarball rcm-*.tar.gz # ... etc. ... And once pushed, you should clean up ./maint/release clean tarball rcm-*.tar.gz # ... etc. ... 4. Build the Debian package: Only on Debian systems can you build the Debian package: make NEWS.md ./maint/release build deb rcm-*.tar.gz ./maint/release push deb rcm-*.tar.gz ./maint/release clean deb rcm-*.tar.gz This will create both a binary and a signed source package. Source packages go in the `deb-src` directory on the `gh-pages` branch. 5. Contact package maintainers: OpenBSD Mike Burns 0x3E6761F72846B014 openSUSE Andrei Dziahel 0x58BA3FA4A49D76C2 Ubuntu Martin Frost 0x4609D1E5ECA538E6 FreeBSD Leonardo Brondani Schenkel 0x0883b5ebf741f50a Korora Carl van Tonder 0xb55275fbcbe8383c Arch Max Falk 0x9cbdc83ba3753845 MacPorts Aljaž Srebrnič 0xe140e1eea54ee677 Debian Eric Collins 0x7BEB44E2771AB877