Thank you Viraj. The time constraint is that ideally, we should fix PHOENIX-6442 for 5.2 and 5.1.2 I'd expect either one to be at least a few weeks out.
We should also have a fix prepared for PHOENIX-6442 first, so that we can check the current Tephra snapshot against it, before releasing 0.16.1. (Even if it can only be committed after the Tephra release) On Tue, Apr 20, 2021 at 9:48 AM Viraj Jasani <[email protected]> wrote: > Although I have not used Tephra and has very limited knowledge, if the > upcoming release is not strictly time bound, I can volunteer to be RM for > 0.16.1/0.17.0 and learn a couple of things about Tephra. > > > On Tue, 20 Apr 2021 at 6:14 AM, Josh Elser <[email protected]> wrote: > > > All points look good to me :) > > > > On 4/19/21 4:31 AM, Istvan Toth wrote: > > > Hi! > > > > > > Due to low interest, Tephra support tends to be broken on master (and > in > > > this case, on recent releases). > > > > > > The current problems with Tephra integration are described in > > PHOENIX-6442. > > > > > > However, before we can fix that, we need to have a Tephra release that > > > supports HBase 2.4. > > > > > > As the changes since 0.16.0 are minimal, I propose calling it 0.16.1 . > > > > > > Please use this thread to share your suggestions, objections, or > > concerns, > > > or volunteer to the RM for the release. > > > > > > If there is no objection, and no other volunteer to act as a release > > > manager, I will start the release process as my time permits (probably > > > sometime next week). > > > > > > regards > > > Istvan > > > > > > -- *István Tóth* | Staff Software Engineer [email protected] <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> <https://www.cloudera.com/> ------------------------------
