...
- Check out the release branch with:
Code Block svn co https://svn.apache.org/repos/asf/hive/branches/branch-X.Y
- Update
CHANGES.txt
to include the release version and date (this change must be committed to trunk and any intermediate branches between trunk and the branch being released). - Update the
version
property value in thebuild.properties
file. You should remove theSNAPSHOT
suffix and setversion
equal tohive-X.Y.Z
where 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). - Commit these changes.
Code Block svn commit -m "Preparing for release X.Y.Z"
- If not already done, merge desired patches from trunk into the branch and commit these changes. You can find the revision numbers using
svn log CHANGES.txt
in the branch and in trunk. We don't currently use svn merge for this, but if we did, the script would beCode Block cd branch-X.Y svn merge -rR1:R2 ../trunk . svn commit -m "Merge -r R1:R2 from trunk to X.Y branch. Fixes: HIVE-A, HIVE-B."
- 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 JIRA's 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.)
- Tag the release candidate (R is the release candidate number, and also starts from 0):
Code Block svn copy https://svn.apache.org/repos/asf/hive/branches/branch-X.Y \ https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR release."
...