[jira] [Comment Edited] (HBASE-22076) Move version on from 2.2.0 to 2.2.1-SNAPSHOT

["Duo Zhang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-22076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797837#comment-16797837 ] 

Duo Zhang edited comment on HBASE-22076 at 3/21/19 5:13 AM:
------------------------------------------------------------

In general I do not think we need to this in the release scripts...

In the past I just do this:

1. Set the version to x.x.x, i.e, remove the -SNAPSHOT suffix, it will be an issue on jira.
2. Do everything for a release.
3. Set the version to x.x.x-SNAPSHOT, it will be another issue on jira.

In step 2, we may push out several RCs, and the version is always x.x.x, so I do not think we need to change the versions in all the pom when we make a RC?

Thanks.


was (Author: apache9):
In general I do not think we need to this in the release scripts...

In the past I just do this:

1. Set the version to x.x.x, i.e, remove the -SNAPSHOT suffix, it will be an issue.
2. Do everything for a release.
3. Set the version to x.x.x-SNAPSHOT.

In step 2, we may push out several RCs, and the version is always x.x.x, so I do not think we need to change the versions in all the pom when we make a RC?

Thanks.

> 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)