Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Sean Busbey
On Wed, Jun 7, 2017 at 2:31 PM, Stack wrote: > On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell wrote: > >> Thanks. >> I'd like to see us RM branch-2, branch-1, and master and get away from >> narrow focus on the branch-x.y branches that only produce patch releases. >> Seems a better use of RM ban

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Enis Söztutar
Above plan: * branch-2 made off of master * alpha/beta releases tagged off of branch-2 * branch-2.0 made off of branch-2 * 2.0.0 GA release tagged off of branch-2.0 * Follow on minor releases branch-2.y off of branch-2 Looks good. That is what we have done for 1.0/branch-1 as well. The only thing

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Stack
On Wed, Jun 7, 2017 at 1:19 PM, Jonathan Hsieh wrote: > +1 for 2.0.0-alpha1. It would be really helpful for dependent projects > getting started against the updated apis (e.g. removed deprecated apis). > > Let me push up a rough cut as an RC. Lets see how we do. St.Ack > Jon > > On Wed, Jun 7

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Jonathan Hsieh
+1 for 2.0.0-alpha1. It would be really helpful for dependent projects getting started against the updated apis (e.g. removed deprecated apis). Jon On Wed, Jun 7, 2017 at 12:31 PM, Stack wrote: > On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell > wrote: > > > Thanks. > > I'd like to see us RM

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Stack
On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell wrote: > Thanks. > I'd like to see us RM branch-2, branch-1, and master and get away from > narrow focus on the branch-x.y branches that only produce patch releases. > Seems a better use of RM bandwidth to supervise a whole code line. > > I like thi

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Andrew Purtell
Thanks. I'd like to see us RM branch-2, branch-1, and master and get away from narrow focus on the branch-x.y branches that only produce patch releases. Seems a better use of RM bandwidth to supervise a whole code line. On Wed, Jun 7, 2017 at 9:52 AM, Stack wrote: > On Wed, Jun 7, 2017 at 8:09 A

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Stack
On Wed, Jun 7, 2017 at 8:09 AM, Sean Busbey wrote: I liked Josh's question on where is the hbase-2.0 branch and the reminder on the Andrew suggestion that we shift release version emphasis left a digit. Lets try it in hbase-2. > > Thinking about this more, did we document the branching strategy

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Josh Elser
On 6/7/17 11:15 AM, Sean Busbey wrote: On Wed, Jun 7, 2017 at 10:08 AM, Josh Elser wrote: On 6/7/17 11:04 AM, Josh Elser wrote: On 6/7/17 1:17 AM, Stack wrote: Lets start in on the hardening of hbase-2.0.0. All features are in though in need of test and polish. There are tasks outstand

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Sean Busbey
On Wed, Jun 7, 2017 at 10:08 AM, Josh Elser wrote: > > On 6/7/17 11:04 AM, Josh Elser wrote: >> >> >> >> On 6/7/17 1:17 AM, Stack wrote: >>> >>> Lets start in on the hardening of hbase-2.0.0. All features are in though >>> in need of test and polish. There are tasks outstanding around migration >>

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Sean Busbey
On Wed, Jun 7, 2017 at 10:07 AM, Sean Busbey wrote: > On Wed, Jun 7, 2017 at 10:04 AM, Josh Elser 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

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Josh Elser
On 6/7/17 11:04 AM, Josh Elser wrote: On 6/7/17 1:17 AM, Stack wrote: Lets start in on the hardening of hbase-2.0.0. All features are in though in need of test and polish. There are tasks outstanding around migration from hbase-1 to hbase-2 and narratives to tell our users around timeout, etc

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Sean Busbey
On Wed, Jun 7, 2017 at 10:04 AM, Josh Elser 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 e

Re: NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-07 Thread Josh Elser
On 6/7/17 1:17 AM, Stack wrote: Lets start in on the hardening of hbase-2.0.0. All features are in though in need of test and polish. There are tasks outstanding around migration from hbase-1 to hbase-2 and narratives to tell our users around timeout, etc. We still need to update dependencies,

NOTICE: I just created branch-2, the branch from where we'll cut hbase-2.0.0

2017-06-06 Thread Stack
Lets start in on the hardening of hbase-2.0.0. All features are in though in need of test and polish. There are tasks outstanding around migration from hbase-1 to hbase-2 and narratives to tell our users around timeout, etc. We still need to update dependencies, revamp defaults, etc., but the hbase