Versions Compared

Old Version 5

changes.mady.by.user Unknown User (zwoop)

Saved on

compared with

New Version 6

changes.mady.by.user Unknown User (zwoop)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Versioning is controlled in the configure.ac file, it should be the only file necessary to be modified to change the release version number.

RAT reports

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

It's up to the release manager to assure that there are no RAT issues unresolved before making a release.

Creating a release

After updating the versioning in configure.ac:

...

This is the preferred (and recommended) way of creating a release candidate. The release artifact should always be accompanied with the checksums and signature. All release managers must update the KEYS file with their public key, as well as pushing their key to at least one GPG key server.

RAT reports

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

It's up to the release manager to assure that there are no RAT issues unresolved before making a release.

Voting

A new release candidate should be uploaded into a "personal" area, typically something like http://people.apache.org/~someuser/. Once available, a vote should be started on the dev@trafficserver.apache.org mailing list, and run for 72 hours. After the vote has passed, the artifact can be moved from the personal area to the distribution servers (see next section).

...