Table of Contents
Releases
Expectations
When a release branch is created, it is understood that the first release on that branch will support some set of platforms. It is expected that all later releases cut from that branch (a release family) will support the same set of platforms as the first release cut from that branch. So, for instance, if 10.X.1 supports Java 6, 7, and 8, then it is expected that 10.X.2, 10.X.3, etc. will all support Java 6, 7, and 8.
High level time line
- Volunteer to manage the release.
- Verify that your environment has all the tools you need to generate a release.
- Publish and correct the Release Notes.
For each release candidate:
- Adjust Release Notes as necessary.
- Adjust JIRA release ids and fix showstoppers which flunked the previous release candidate.
- Build new distributions and call a vote to vet them.
Once after candidate passes vote:
- Deploy distributions to the Apache mirrors.
- Deploy distributions to the maven repository.
- Tag the release and update miscellaneous references.
- Announce the new release.
Release process steps details
Preparation
See ReleasePrep
Release Candidates
Publication
Announce CVEs
If the release contains fixes for CVEs, you will need to announce them. See Announcing CVEs.