This page is prepared for Hive committers. You need committer rights to create a new Hive release.
- Bulk update Jira to unassign from this release all issues that are open non-blockers and send follow-up notification to the developer list that this was done.
- Run 'ant rat' to and examine the generated report for any files, especially .java files should be having Apache license headers. Add the license header to any file that is missing it (open a jira and submit a patch).
- Update copyright date in NOTICE. If the components mentioned in them have updated version, you would need to update the copyright dates for those. (Thejas comment: It sounds like entries are needed in NOTICE only if the license requires such attribution . See - http://www.apache.org/legal/src-headers.html#notice.)
Skip this section if this is NOT the first release in a series (i.e., release X.Y.0).
Notify developers on the #hive IRC channel and dev@hive mailing lists that you are about to branch a release.
Create a branch for the release series:
Increment the value of the
versionproperty in all pom.xml files. For example, if the current value is
0.7.0-SNAPSHOT, the new value should be
0.8.0-SNAPSHOT. Please note that the
SNAPSHOTsuffix is required in order to indicate that this is an unreleased development branch. This can be accomplished with a single command using Maven's Versions plugin as follows:
- Make changes to metastore upgrade scripts. See HIVE-6555 on how this was done for HIVE 0.13.
- Verify that the build is working with changes.
Commit these changes to trunk.
Updating Release Branch
These operations take place in the release branch.
Check out the release branch with:
versionproperty value in all pom.xml files. You should remove the
SNAPSHOTsuffix and set
hive-X.Y.Zwhere Z is the point release number in this release series (0 for the first one, in which case this step is a no-op since you already did this above when creating the branch). Use Maven's Versions plugin to do this as follows:
- Update the the value of the
TRACKING_BRANCHfield in the
.reviewboardrcfile to point to the
- Verify that the build is working with changes.
Commit these changes.
If not already done, merge desired patches from trunk into the branch and commit these changes. We don't currently use svn merge for this, but if we did, the script would be
- You probably also want to commit a patch (on both trunk and branch) which updates README.txt to bring it up to date (at a minimum, search+replacing references to the version number). Also check NOTICE to see if anything needs to be updated for recent library dependency changes or additions.
- Select all of the JIRAs for the current release that aren't FIXED and do bulk update to clear the 'Fixed Version' field.
- Likewise, use JIRA's Release Notes link to generate content for the RELEASE_NOTES.txt file. Be sure to select 'Text' format. (It's OK to do this with a direct commit rather than a patch.)
- Update the release notes in trunk with the release notes in branch.
Tag the release candidate (R is the release candidate number, and also starts from 0):
- Make sure your release notes have been updated for any new commits, and go through the previous steps if necessary.
Build the release (binary and source versions) after running unit tests. Manually create the md5 files. On a Mac use md5 in place of md5sum.
Verify that the MD5 checksums are valid:
- Check that release file looks ok -- e.g., install it and run examples from tutorial.
- Setup your PGP keys for signing the release, if you don't have them already.
Sign the release (see Step-By-Step Guide to Mirroring Releases for more information).
Copy release files to a public place.
Publish Maven artifacts to the Apache staging repository:
- Login to the Apache Nexus server and "close" the staged repository. This makes the artifacts available at a temporary URL.
Call a release vote on dev at hive.apache.org.
Verifying the Release Candidate
Verifying the PGP signature:
- Verifying the md5 checksum:
See the step under Building.
Once three PMC members have voted for a release, it may be published.
Tag the release:
Copy release files to the distribution directory and make them writable by the
The release directory usually contains just two releases, the most recent from two branches, with a link named 'stable' to the most recent recommended version.
- Wait 24 hours for release to propagate to mirrors.
Prepare to edit the website.
Copy the new release docs to
If this is a bugfix release, delete the documentation for the obsoleted release.
- Update the documentation links in
- Update the release news in
publish/.htaccesswith the current release and any new redirects for obsoleted releases.
Regenerate the site, review it, then commit it. The live site is automatically deployed from subversion after a few minutes.
- Update JIRA
- Ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
- Release the version. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in Hive's Jira for this step and the next.
- Close issues resolved in the release. Disable mail notifications for this bulk change.
- Login to the Apache Nexus server and mark the release candidate artifacts as released.
Send a release announcement to Hive
devlists as well as the Apache
announcelist. This email should be sent from your Apache email address: