The big feature I'm tracking is HBase 3.0 support. I'm fine with releasing 5.3.0 before HBase 3.0 is out, but then we should be prepared to either add HBase 3 support in a patch release, or release 5.4.0 relatively quickly after 3.0. (Summer/Autumn-ish)
There are still three HBase 3.0 preparation patches by me and Villo, which IMO should be in 5.3.0, otherwise backports will be harder than they should be. These have been waiting for review for some months, If I can't find anyone to review them, then I will self-review, as technically their current iteration was already rebased/re-worked by Villo. https://github.com/apache/phoenix/pull/2035 https://github.com/apache/phoenix/pull/2036 https://github.com/apache/phoenix/pull/2038 The other major outstanding issue is the spotless reformat. I think we should do that before branching, otherwise it's just a lot of extra work to do that twice. (The spotless reformat, and the big outstanding HBase 3.0 preparation patches are another problem, as it would be a lot of work to rebase them after the reformat) Istvan On Fri, Apr 18, 2025 at 2:06 AM Viraj Jasani <vjas...@apache.org> wrote: > Hi, > > I am looking forward to creating the 5.3 branch from the master branch > sometime next week. > > We have many large changes in the master branch. While majority features > are hidden behind flags, it is important to ensure we have a smooth > release. > > Please discuss here if there are any big changes you are planning to > include with the 5.3.0 release. > -- *István Tóth* | Sr. Staff Software Engineer *Email*: st...@cloudera.com cloudera.com <https://www.cloudera.com> [image: Cloudera] <https://www.cloudera.com/> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image: Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera on LinkedIn] <https://www.linkedin.com/company/cloudera> ------------------------------ ------------------------------
