[
https://issues.apache.org/jira/browse/HIVE-16301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947621#comment-15947621
]
Naveen Gangam commented on HIVE-16301:
--------------------------------------
[~pxiong] Yes, I was unaware of this documentation but I used maven's
versions:set command, slightly different command thought {{mvn versions:set
-DnewVersion=2.3.0-SNAPSHOT -DoldVersion=2.2.0-SNAPSHOT
-DgenerateBackupPoms=false}} to update the POMs. But for some reason, I thought
it did not update the {{hive.version.shortname}} that I had to do it manually.
Since I am not creating a new release branch, and just updating the release
version of the current dev branch, step #8 isnt applicable to me. Correct me if
I am wrong.
> Prepare branch-2 for 2.3 development.
> -------------------------------------
>
> Key: HIVE-16301
> URL: https://issues.apache.org/jira/browse/HIVE-16301
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 2.3.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Blocker
> Attachments: HIVE-16301.2.patch, HIVE-16301.patch
>
>
> branch-2 is now being used for 2.3.0 development. The build files will need
> to reflect this change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
