...
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
Increment the
version
property value in all pom.xml files and add theSNAPSHOT
suffix. For example, if the released version was0.7.0
, the new value should be0.7.1-SNAPSHOT
. Please note that theSNAPSHOT
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 language text mvn versions:set -DnewVersion=0.7.1-SNAPSHOT -DgenerateBackupPoms=false
- 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
andstandalone-metastore/pom.xml
search for the propertyhive.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. - Verify that the build is working with changes.
Commit these changes with a comment "Preparing for X.Y.Z+1 development".
...