Release Process

Release Process for mod_auth_gssapi

The process is currently quite simple and requires write access to the project's git repository.

Prepare the sources

Version and Tag the release

• Commit a changed version.m4 with the new version number (ex. 0.1.0)

• Test locally with "make test" that everything builds fine

• Tag the release in master like this:

git tag v0.1.0

This will apply the tag to the last commit

• Push the tag:

git push origin v0.1.0

Create a release tarball and SHA hash

• Run the following commands (on a git clean tree, please):

autoreconf -f -i && ./configure && make distcheck

... will generate a tarball named like: mod_auth_gssapi-0.1.0.tar.gz

sha512sum mod_auth_gssapi-0.1.0.tar.gz > mod_auth_gssapi-0.1.0.tar.gz.sha512sum.txt

... will generate a file with a sha512 checksum

Publish the release

• Create a Release page with highlights and a full changelog with the command:

git shortlog ..

• Upload the release files attaching them to the new release page. (We do this because github has no stable tarballs, the tarball you get from a release tag is generated on the fly and cached for a small period of time, once the cache expire a new tarball is generated and checksums will not match anymore).