Versions Compared

Old Version 57

changes.mady.by.user Jesús Camacho Rodríguez

Saved on

compared with

New Version 58

changes.mady.by.user Lefty Leverenz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: trivial edits in "Preparing Branch for Future Maintenance Release" (thanks for the new section, Jesús)

...

After the release has been completed, we should prepare the branch for the next development cycle.

  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. Verify that the build is working with changes.

  4. Commit these changes with a comment "Preparing for X.Y.Z+1 development".

...

See Also