[
https://issues.apache.org/jira/browse/HBASE-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797835#comment-16797835
]
stack commented on HBASE-22076:
-------------------------------
bq. Sorry sir, this has to be reverted. We still have some blockers for 2.2.0,
for example HBASE-22060.
I think its ok. Let me say why.
When we make the next RC, the RC script over in HBASE-21935, will check out
branch-2.2. As part of the first stage, the tagging step, it will set the pom
version to whatever you tell it the RC target is, update the release notes, tag
it, and push it. It will then move on the pom version and commit that. For
example, if the RC to build is 2.2.0RC1, it will set the pom version to 2.2.0,
update the CHANGES.md and RELEASENOTES.md pulling whatever is marked 2.2.0 in
JIRA at the time (courtesy of yetus), push the changes, tag the repo w/
2.2.0RC1, then set the pom version to the next version+SNAPSHOT and commit that.
{code}
update_releasenotes `pwd`/hbase "$RELEASE_VERSION"
cd hbase
git config user.name "$GIT_NAME"
git config user.email $GIT_EMAIL
# Create release version
$MVN versions:set -DnewVersion=$RELEASE_VERSION | grep -v "no value" # silence
logs
git add RELEASENOTES.md CHANGES.md
git commit -a -m "Preparing HBase release $RELEASE_TAG; tagging and updates to
CHANGES.md and RELEASENOTES.md"
echo "Creating tag $RELEASE_TAG at the head of $GIT_BRANCH"
git tag $RELEASE_TAG
# Create next version
$MVN versions:set -DnewVersion=$NEXT_VERSION | grep -v "no value" # silence
logs
git commit -a -m "Preparing development version $NEXT_VERSION"
{code}
If the RC passes, the pom version is set properly. Otherwise, we do above cycle
again. That the pom version is in advance of the release is a little odd but I
think its ok. What you think?
I could I suppose set the pom to current version plus '-SNAPSHOT' instead of
the next version plus -SNAPSHOT. Would mean extra step after release setting
pom versions to next version....
> Move version on from 2.2.0 to 2.2.1-SNAPSHOT
> --------------------------------------------
>
> Key: HBASE-22076
> URL: https://issues.apache.org/jira/browse/HBASE-22076
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Priority: Major
>
> Moving on the pom version. Doing this because the script that makes RCs fails
> otherwise; it needs to work against a version that ends in -SNAPSHOT. The
> script takes care of setting the version appropriately as it builds. FYI
> [~zghaobac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
