This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • HowToRelease

Versions Compared

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. Increment the version property value in all pom.xml files and add the SNAPSHOT suffix. For example, if the released version was 0.7.0, the new value should be 0.7.1-SNAPSHOT. Please note that the SNAPSHOT suffix is required in order to indicate that this is an unreleased development branch. Use Maven's Versions plugin to do this as follows:

    Code Block
    languagetext
    mvn versions:set -DnewVersion=0.7.1-SNAPSHOT -DgenerateBackupPoms=false


  3. If the release number you are preparing moves the major (first) or minor (second) number, update the Hive version name in the poms.  In both pom.xml and standalone-metastore/pom.xml search for the property hive.version.shortname.  This should match the new version number.  
    For example, if you are working on branch-3 and have just released Hive 3.2 and are preparing the branch for Hive 3.3 development, you need to update both poms to have <hive.version.shortname>3.3.0</hive.shortname.version>.  If however you are working on branch-3.1 and have just released Hive 3.1.2 and are preparing the branch for 3.1.3 development, this is not necessary.
  4. Verify that the build is working with changes.
  5. Commit these changes with a comment "Preparing for X.Y.Z+1 development".

...