I think sync replication is a big enough feature for a major release, but I do not think it is production ready... We have back ported the feature to our internal branch which is based on branch-2, but haven't used it yet...
And I also want to land HBASE-21512, which can greatly reduce our client code base, in HBASE-21723 we can remove more than 20k lines of code. And maybe HBASE-21879? Which is good for off heap handling and performance. And also CCSMap? Sean Busbey <[email protected]> 于2019年4月25日周四 下午10:55写道： > Hi folks! > > We're about a year from when HBase 2.0.0 went GA. I'd like to start > cutting alpha releases of 3.0.0 off of the master branch soon. > (expressly I do not want to create another branch, so for now anything > landing in master would be "in" for 3.0.0. hence the "alpha" > designation.) > > I was going to wait for one of the HBase 2 releases to get the stable > label. But lately I don't have a good sense of if that will happen > within a month or within six months, so I'm leaning away from waiting. > > I personally don't have a particular feature I'm trying to get out the > door. I just think we're at risk of another waiting-too-long for a > major release and want to get started on the work of quantifying > what's changed and figuring out how downstream projects are impacted. > I find that all much easier to do when there's a release artifact to > reference. > > I'm happy to just cut alpha releases until someone shows up with a > specific feature need. At that point we can come up with criteria for > entering and exiting beta releases. > > What do folks plan to work on getting ready that needs happen in a > major release? >
