Versions Compared

Old Version 60

changes.mady.by.user Owen O'Malley

Saved on

compared with

New Version 61

changes.mady.by.user Vaibhav Gumashta

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Check out the release branch with:

    Code Block
    languagetext
    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
    languagetext
    mvn versions:set -DnewVersion=0.7.0 -DgenerateBackupPoms=false
  3. Update the the value of the TRACKING_BRANCH field in the .reviewboardrc file to point to the origin/branch-X.Y.
  4. Verify that the build is working with changes.

  5. Commit these changes with a comment "Preparing for X.Y.Z developmentrelease".

     

  6. 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.

  7. 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.

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

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

...