And on 3.0, I still think we should land the splittable meta work, as it will introduce some breaking changes so if we can not land it in 3.0, then maybe we can only delay it to 4.0...
Nick Dimiduk <[email protected]> 于2021年5月5日周三 上午12:34写道： > On Fri, Apr 30, 2021 at 5:40 PM 张铎(Duo Zhang) <[email protected]> > wrote: > > > Does anyone have interest in backporting HBASE-22120 to branch-2? > > > > Yes, I think there would be interest in getting your tracing effort onto > branch-2 ; there's quite a few "watchers" on that Jira. > > What about the backup work? Has it stabilized enough for backport? > > Conversely, if we don't have a killer new feature for 2.5, does that mean > it's time for 3.0? > > Andrew Purtell <[email protected]> 于2021年5月1日周六 上午5:46写道： > > > > > Inline > > > > > > On Fri, Apr 30, 2021 at 2:11 PM Nick Dimiduk <[email protected]> > > wrote: > > > > > > > Heya, > > > > > > > > I'd like to have a planning discussion around our 2.x releases. 2.4 > > seems > > > > to be humming along nicely, I think we won't have a need for 2.3 much > > > > longer. Likewise, it seems like it should be time to start planning > > 2.5, > > > > but when I look at the issues unique to that branch [0], I don't see > > the > > > > big new feature that justifies the new minor release. Rather, I see a > > > > number of items that should be backported to a 2.4.x. Do we have a > big > > > new > > > > feature in the works? Should we consider backporting something from > > > master? > > > > Or maybe there's enough minor changes on 2.5 to justify the > release... > > > but > > > > if so, which of them motivate users to upgrade? > > > > > > > > So, to summarize: > > > > > > > > - How much longer do we want to run 2.3? > > > > - What issues in the below query can be backported to 2.4? Any > > > volunteers? > > > > > > > > > > Thanks for starting this discussion, Nick. > > > > > > Looking at that report, issues like HBASE-24305, HBASE-25793, or > > > HBASE-25458 that clean up or reduce interfaces or refactor/move classes > > are > > > probably excluded from a patch release by our guidelines. Conversely, > > they > > > would not provide much value if backported. > > > > > > I also agree that the motivation for 2.5 here is thin as of now. > > Refactors, > > > interface improvements, or deprecation removals will be nice-to-haves > > when > > > there is a 2.5 someday. > > > > > > All the others in the report are either operational improvements that > > would > > > be nice to backport or bug fixes that should be backported. > > > > > > There might be case by case issues with compatibility during the pick > > > backs, but we can deal with them one at a time. > > > > > > If you are looking for a volunteer to do this, as 2.4 RM I am game. > > > > > > > > > - What's the big new feature that motivates 2.5? > > > > > > > > Thanks, > > > > Nick > > > > > > > > [0]: > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20HBASE%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%202.5.0%20AND%20fixVersion%20not%20in%20(2.4.0%2C%202.4.1%2C%202.4.2%2C%202.4.3)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > > > > > > > > > > -- > > > Best regards, > > > Andrew > > > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > > decrepit hands > > > - A23, Crosstalk > > > > > >
