• Created by Unknown User (zwoop), last updated on Mar 01, 2010 1 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The release process is in place to help follow the ASF guidelines for release management.

Branches

All public releases are cut from a release branch, the current release branch is 2.0.x, and all releases have even version numbering. Development (non-public) releases are cut from the trunk, and have odd version numbering.

Tags

For every released artifact, a tag should be created off the appropriate release branch. These tags should be named exactly the same as the version number released, e.g. "2.0.0-alpha".

Creating a release

After updating the versioning in configure.ac:

autoreconf -i && ./configure
gmake dist

Checksums and signing

All artifacts must be accompanied with the appropriate GPG signature, and cryptographic checksums. After generating the artifact, run the following commands:

ARTIFACT="trafficserver-2.0.0-alpha.tar.gz"

md5sum $ARTIFACT  > ${ARTIFACT}.md5
sha1sum $ARTIFACT > ${ARTIFACT}.sha1
gpg  --armor --output ${ARTIFACT}.asc  --detach-sig $file
  • No labels