This document provides steps involved in pre and post (Apache) release of Apache Ranger.
Pre Release Tasks
Ensure that there is no OPEN lira associated with the release
Notify dev list in advance of the release with details on the release such as purpose of release, who will be be release-manager, ….
Create a separate branch for the release (e.g.: ranger-0.6)
In the release branch:
Update all of the version number to release version number (from SNAPSHOT version number)
$ mvn versions:set -DnewVersion=<newReleaseVersion>
Release VOTE Tasks
Build release artifacts
- DEV VOTE
Verify all of the source is ready for release
Able to validate maven install works fine.
Verify LICENSE and NOTICE files for the release is updated based on changes in the release
Update the release notes
Create a tag in the release branch (${release-version}-rc{release-candidate-number}
Create the release artifacts using $ant –f release-build.xml -Dranger–release-version=<new-version-number>)
This should create )target/apache-ranger-incubating-<version-number>.tar.gz* files)
Upload the release artifacts (3 files from target folder) to svn (https://dist.apache.org/repos/dist/dev/incubator/ranger/${new-version}-incubating-rc${release-candidate-number})
If the signer's key is not in KEYS file in https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS, Update the KEYS file to add that the signer key using SVN.
Send release VOTE request to dev@ranger.incubator.apache.org
If VOTE did not go through,
Fix the problem and Repeat the “Build release artifacts” steps again
Send a vote results to dev@ranger.incubator.apache.org , private@ranger.incubator.apache.org via email
IPMC VOTE (This is not required anymore, since Ranger has graduated to a top level project): Update: 30-JAN-2017
Send release VOTE to general@incubator.apache.org
If VOTE did not go through
Fix the problem and Repeat the “Build release artifacts” steps again
Send a vote results to general@incubator.apache.org , private@ranger.incubator.apache.org via email
Post Release Tasks
Copy the source release artifacts to svn - https://dist.apache.org/repos/dist/release/incubator/ranger
Create a final release tag in the release branch (${release-version})
Update the doc site with the release artifacts (use master branch to do this!) and push the changes in the master branch
In Apache JIRA admin, mark the release as complete and create a next version for tracking the changes to the next (major|minor) version
Update version number in source code to next snapshot version
Update the pom.xml version to next SNAPSHOT ($ mvn versions:set -DnewVersion=<nextVersion>-SNAPSHOT)
push the changes to the release branch (e.g. ranger-0.6 for all ranger-0.6.* releases)
If the release resolved any CVE,