• 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 4 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 asf-dist

Checksums and signing

All artifacts must be accompanied with the appropriate GPG signature, and cryptographic checksums. To generate the artifact with the required checksums and signature, do

autoreconf -i && ./configure
gmake asf-dist-sign

RAT reports

The Release Audit Tool Tool reports are automatically generated on both trunk and all active release branches. The current reports are

Uploading

All artifacts, and checksums and signatures, should be checked into the following Subversion directory:

 https://dist.apache.org/repos/dist/release/incubator/trafficserver

Once committed, these files are automatically published to the appropriate areas on people.apache.org.

  • No labels