Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <938b12cf-2e84-0c5b-21f9-8827cb2a894d@apache.org>
References: <CADcMMgGEO2psvPfwZejZRduqW5gf6hf1Sh+PJ2qoNUmdrAWobA@mail.gmail.com>
 <938b12cf-2e84-0c5b-21f9-8827cb2a894d@apache.org>
From: Sean Busbey <busbey@apache.org>
Date: Wed, 7 Jun 2017 10:07:45 -0500
Message-ID: <CAN5cbe72A+Ta4stpO1OPs4T1tOwDc=MzeBhui0vv7tDq7p_erg@mail.gmail.com>
Subject: Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0
To: dev <dev@hbase.apache.org>
Content-Type: text/plain; charset="UTF-8"
archived-at: Wed, 07 Jun 2017 15:08:08 -0000

On Wed, Jun 7, 2017 at 10:04 AM, Josh Elser <elserj@apache.org> wrote:
>
>
> On 6/7/17 1:17 AM, Stack wrote:
>>
>
>> I just set the version on master branch to be 3.0.0-SNAPSHOT.
>
>
> I was just thinking about this one this morning: would master become 2.1.0
> or 3.0.0?
>
> I'd guess that the intent is to put more emphasis on the "x" instead of the
> "y" and "z" (for a version string "x.y.z")? We all on board with that plan
> too, for better or for worse? :)

yeah, this is the same bit we did when branch-1 was created off of
master last major release. We need a place to put the breaking stuff.

Hopefully we can exercise a more planned out approach to how long
master waits for the next branch-x.