You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Sean Busbey (Jira)" <ji...@apache.org> on 2020/05/16 18:22:00 UTC

[jira] [Created] (HBASE-24384) new major version in release script should default compat report to previous latest minor release

Sean Busbey created HBASE-24384:
-----------------------------------

             Summary: new major version in release script should default compat report to previous latest minor release
                 Key: HBASE-24384
                 URL: https://issues.apache.org/jira/browse/HBASE-24384
             Project: HBase
          Issue Type: Improvement
          Components: community
            Reporter: Sean Busbey


currently if you are starting a new major version, the default calculated comparison version is invalid:

{code}

========================
=== Gathering release details.

PROJECT [hbase]: hbase
GIT_BRANCH [branch-2.3]: master
Current branch VERSION is 3.0.0-SNAPSHOT.
RELEASE_VERSION [3.0.0]: 3.0.0-alpha-1
NEXT_VERSION [3.0.1-SNAPSHOT]: 3.0.0-alpha-2-SNAPSHOT
RC_COUNT [0]: 
RELEASE_TAG [3.0.0-alpha-1RC0]: 
This is a dry run. If tag does not actually exist, please confirm the ref that will be built for testing.
GIT_REF [3.0.0-alpha-1RC0]: 
api_diff_tag [rel/3.0.-2]: rel/2.2.4
{code}

when the new version is a new major we should either default to the prior initial major release (e.g. 2.0.0) or we should scan the release metadata for the most recent release from the prior major release (e.g. 2.2.4).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)