I'll start branch-2.0 (I can do branch-2.1 too Duo...). Let's make 2.0.6 the last release on branch-2.0. We have too many branches (smile).I was going to make sure I could upgrade to a 2.2 release from 2.0.... as part of checking of 2.0.6RC.
Regards adding more server-side support for HBCK2 in branch-2.0, as is, 2.0.6 will have a bunch of new HBCK2 changes (See HBASE-21475) including the new hbck report page added by Guanghao. If more is needed post branch-2.0 EOL, HBCK2 client-side fixup is being added still to cover releases that are missing server-side additions whether branch-2.0, branch-2.1 or branch-2.2. Though inferior to server-side equivalents, they may be enough for the branch-2.0 operator. Hopefully users have also been moving off branch-2.0 to the later releases. Thanks, S On Tue, Aug 6, 2019 at 6:26 AM 张铎(Duo Zhang) <[email protected]> wrote: > Not sure as we still have some pending HBCK fixes... > > Maybe we will also have a 2.0.7? Depending on the release manager... > > Sean Busbey <[email protected]> 于2019年8月6日周二 下午9:12写道： > > > this this still going to be the final 2.0.x release? Wasn't that the > > plan, a single post-2.2.0 release? > > > > On Tue, Aug 6, 2019 at 2:49 AM 张铎(Duo Zhang) <[email protected]> > > wrote: > > > > > > Due to the jackson CVE, and also, there is a critical bug fix > > HBASE-22539. > > > > > > I can take care of 2.1.6, and Guanghao Zhang is the release manager for > > > 2.2.x, Stack is the release manager for 2.0.x, so by default they > should > > > take care of the new releases. > > > > > > Shout if you do not have enough time to make a release, then we can > find > > > other volunteers to make the new releases. > > > > > > Thanks. > > >
