Page History

...

1. Notify developers on the #hive IRC channel and dev@hive mailing lists that you are about to branch a release.

2. Create a branch for the release series: 

   Code Block
   language text
   git checkout -b branch-X.Y origin/master git push -u origin branch-X.Y

3. Remove the storage-api from the list of modules to build in the top level pom.xml. Set the storage-api.version property to the release of storage-api that you are using for your release.

4. Increment the value of the version property 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 SNAPSHOT suffix 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: 

5. Code Block
   language text
   mvn versions:set -DnewVersion=X.Y.0-SNAPSHOT -DgenerateBackupPoms=false

6. Make changes to metastore upgrade scripts. See HIVE-6555 on how this was done for HIVE 0.13.
7. Verify that the build is working with changes.

8. Commit these changes to master with a comment "Preparing for X.Y+1.0 development".

...

1. Check out the release branch with:

   Code Block
   language text
   git clone https://git-wip-us.apache.org/repos/asf/hive.git/ <hive_src_dir> cd <hive_src_dir> git checkout branch-X.Y

2. Update the version property value in all pom.xml files. You should remove the SNAPSHOT suffix and set version equal to hive-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). Use Maven's Versions plugin to do this as follows:

   Code Block
   language text
   mvn versions:set -DnewVersion=0.7.0 -DgenerateBackupPoms=false

3. Remove the storage-api from the list of modules to build in the top level pom.xml. Set the storage-api.version property to the release of storage-api that you are using for your release. Make sure to set the storage-api.version property in standalone-metastore/pom.xml as well.

4. Update the the value of the TRACKING_BRANCH field in the .reviewboardrc file to point to the origin/branch-X.Y.
5. Verify that the build is working with changes.

6. Commit these changes with a comment "Preparing for X.Y.Z release".

    

7. If not already done, merge desired patches from trunk into the branch and commit these changes. Avoid usage of "git merge" to avoid too many merge commits. Either request the committer who committed that patch in master to commit to this branch, or commit it yourself, or try doing a git cherry-pick for trivial patches. Specifics of this step can be laid down by the release manager.

8. 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.
   1. Select all of the JIRAs for the current release that aren't FIXED and do bulk update to clear the 'Fixed Version' field.
   2. 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.)
   3. Update the release notes in trunk with the release notes in branch.

9. Tag the release candidate (R is the release candidate number, and also starts from 0):

   Code Block
   language text
   git tag -a release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR release." git push origin release-X.Y.Z-rcR

...