Re: On the 2.1.0 and 3.0.0 release

Pushed branch-2.1 at this commit. commit a86141b6252a433ff62f5c1979d7523031da0bf2 Author: zhangduo Date: Thu Jun 21 10:14:57 2018 +0800 HBASE-20752 Make sure the regions are truly reopened after ReopenTableRegionsProcedure 2018-06-22 15:10 GMT+08:00 张铎(Duo Zhang) : > Hold on committing

Re: On the 2.1.0 and 3.0.0 release

Hold on committing to branch-2. Will cut branch-2.1 soon. 2018-06-19 22:05 GMT+08:00 张铎(Duo Zhang) : > Moved a bunch of issues out of 2.1.0. You can add it back if you think > this is important for 2.1.0 release but we need to be quick. Will cut > branch-2.1 after finish the related issues

Re: On the 2.1.0 and 3.0.0 release

Moved a bunch of issues out of 2.1.0. You can add it back if you think this is important for 2.1.0 release but we need to be quick. Will cut branch-2.1 after finish the related issues around SCP and MRP, maybe end of this week. Thanks. 2018-06-13 15:00 GMT+08:00 张铎(Duo Zhang) : > I set

Re: On the 2.1.0 and 3.0.0 release

I set HBASE-20708 as a blocker for 2.1.0 release, and I also think we need to address HBASE-20706. Will keep working on it. 2018-06-13 14:11 GMT+08:00 Stack : > On Sun, Jun 3, 2018 at 8:54 PM 张铎(Duo Zhang) > wrote: > > > What;s your plan sir? Branch branch-2.1 from branch-2.0? > > > > > Dang.

Re: On the 2.1.0 and 3.0.0 release

On Sun, Jun 3, 2018 at 8:54 PM 张铎(Duo Zhang) wrote: > What;s your plan sir? Branch branch-2.1 from branch-2.0? > > Dang. Its time to push out a new release -- it is > 6 weeks since 2.0.0 -- but I'll just call it 2.0.1. It has 70+ fixes in it which is an awful lot for a patch release (It is our

Re: On the 2.1.0 and 3.0.0 release

https://issues.apache.org/jira/browse/HBASE-20682 This is a big problem for both branch-2 and branch-2.0 so will wait for a bit until we can make sure there is no problem. Hope this could be done this week. 2018-06-05 9:35 GMT+08:00 张铎(Duo Zhang) : > Anyway for 3.0 I think we need to have

Re: On the 2.1.0 and 3.0.0 release

Anyway for 3.0 I think we need to have something new. And I think we could make use of feature branch more, so it will not delay the release. We can focus on the progress of the most important features and make sure they can be done before the release, and for other features, just do not merge

Re: On the 2.1.0 and 3.0.0 release

On 6/4/18 12:16 AM, Stack wrote: On Sun, Jun 3, 2018 at 8:54 PM, 张铎(Duo Zhang) wrote: What;s your plan sir? Branch branch-2.1 from branch-2.0? Its a suggestion. I like Andrew's notion that we left-shift how we have been thinking about version numbers; that we releases tend toward minor

Re: On the 2.1.0 and 3.0.0 release

I think it is expected that we have more patch releases for minor releases like 2.0.x and 1.1.x. As a new major release is expected to be unstable in the beginning. Even if we want to retire 2.0.x ASAP, I still think we need a have a 2.0.1 release... Stack 于2018年6月4日 周一12:16写道： > On Sun, Jun 3,

Re: On the 2.1.0 and 3.0.0 release

On Sun, Jun 3, 2018 at 8:54 PM, 张铎(Duo Zhang) wrote: > What;s your plan sir? Branch branch-2.1 from branch-2.0? > > Its a suggestion. I like Andrew's notion that we left-shift how we have been thinking about version numbers; that we releases tend toward minor increments rather than patch

Re: On the 2.1.0 and 3.0.0 release

What;s your plan sir? Branch branch-2.1 from branch-2.0? 2018-06-04 11:50 GMT+08:00 Stack : > On Sun, Jun 3, 2018 at 5:36 PM, 张铎(Duo Zhang) > wrote: > > > Will cut the 2.1 branch tomorrow if no objections. The unfinished > features > > will be disabled by default or purged from branch-2.1 and

Re: On the 2.1.0 and 3.0.0 release

On Sun, Jun 3, 2018 at 5:36 PM, 张铎(Duo Zhang) wrote: > Will cut the 2.1 branch tomorrow if no objections. The unfinished features > will be disabled by default or purged from branch-2.1 and target to 2.2 > release. > > I was thinking that the next release off branch-2.0 could be 2.1.0. It has

Re: On the 2.1.0 and 3.0.0 release

Also, can you document 2.0 to 2.1? (even if there are no special steps) :) Nice to see you continuing to push on 2.1, Duo! On 6/3/18 10:09 PM, 张铎(Duo Zhang) wrote: Serial replication will be fine. And also I will do some work on document how to rolling upgrade from 1.x to 2.1. 2018-06-04 9:55

Re: On the 2.1.0 and 3.0.0 release

Serial replication will be fine. And also I will do some work on document how to rolling upgrade from 1.x to 2.1. 2018-06-04 9:55 GMT+08:00 Mike Drob : > Do you have an idea already of which features are making the cut? > > On Sun, Jun 3, 2018, 7:36 PM 张铎(Duo Zhang) wrote: > > > Will cut the

Re: On the 2.1.0 and 3.0.0 release

Do you have an idea already of which features are making the cut? On Sun, Jun 3, 2018, 7:36 PM 张铎(Duo Zhang) wrote: > Will cut the 2.1 branch tomorrow if no objections. The unfinished features > will be disabled by default or purged from branch-2.1 and target to 2.2 > release. > > 2018-05-17

Re: On the 2.1.0 and 3.0.0 release

Will cut the 2.1 branch tomorrow if no objections. The unfinished features will be disabled by default or purged from branch-2.1 and target to 2.2 release. 2018-05-17 14:19 GMT+08:00 张铎(Duo Zhang) : > Plan to cut branch-2.1 at the end of May. Will consider the status of the > new features at

Re: On the 2.1.0 and 3.0.0 release

Plan to cut branch-2.1 at the end of May. Will consider the status of the new features at that time to determine what will be released with 2.1.x release line. 2018-05-08 10:16 GMT+08:00 Josh Elser : > Big big big +1 > > (Came in to say just this but you beat me to it :D) > >

Re: On the 2.1.0 and 3.0.0 release

Big big big +1 (Came in to say just this but you beat me to it :D) On 5/7/18 12:07 AM, 张铎(Duo Zhang) wrote: Let's do big features in 3.0.0 only. Ideally there will no big new features for a minor release, so that we can move the stable pointer to newer minor versions quickly and retire the

Re: On the 2.1.0 and 3.0.0 release

On Mon, May 7, 2018 at 2:15 AM, Yu Li wrote: > bq. As I volunteered to be the release manager for the 2.1 release line > I guess we could expect another great release line (smile) > > Yep! > bq. For the 2.1 release line... > I could see more "Punted out of 2.0" features in

Re: On the 2.1.0 and 3.0.0 release

>We disabled it by default in the end due to some performance issues... Thanks for the info. I missed the party. :( On 2018/05/07 06:41:51, 张铎(Duo Zhang) wrote: > 2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai : > > > > As I volunteered to be the release

Re: On the 2.1.0 and 3.0.0 release

bq. As I volunteered to be the release manager for the 2.1 release line I guess we could expect another great release line (smile) bq. For the 2.1 release line... I could see more "Punted out of 2.0" features in our 2.0 doc

Re: On the 2.1.0 and 3.0.0 release

Let's do big features in 3.0.0 only. Ideally there will no big new features for a minor release, so that we can move the stable pointer to newer minor versions quickly and retire the old branches. It will be a nightmare if we have lots of active minor release lines... 2018-05-07 14:53 GMT+08:00

Re: On the 2.1.0 and 3.0.0 release

Why 2.1 doesn't contatin synchronous replication? This can be a experiment feature in 2.1? 2018-05-07 14:41 GMT+08:00 张铎(Duo Zhang) : > 2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai : > > > > As I volunteered to be the release manager for the 2.1 release

Re: On the 2.1.0 and 3.0.0 release

2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai : > > As I volunteered to be the release manager for the 2.1 release line so > let > > me bring this up. > +1 to Duo be RM of 2.1 release. > > > disabled from 2.0.0 release, for example, serial replication, and in > memory compaction

Re: On the 2.1.0 and 3.0.0 release

> As I volunteered to be the release manager for the 2.1 release line so let > me bring this up. +1 to Duo be RM of 2.1 release. > disabled from 2.0.0 release, for example, serial replication, and in memory > compaction IIRC, in memory compaction is enabled in 2.0 and the default policy is

On the 2.1.0 and 3.0.0 release

As I volunteered to be the release manager for the 2.1 release line so let me bring this up. For the 2.1 release line, I would like to define it as the 'real' 2.x version of HBase. It should include the features which are reverted or disabled from 2.0.0 release, for example, serial replication,