Keeping the thread alive, we haven't gotten an objection, and no-one volunteered to maintain 4.x, so maybe we can go ahead with the EOL process ? I think that we've already had a consensus on the previous discussions, apart from the SFDC usage, which is now also resolved.
Istvan On Thu, Apr 14, 2022 at 3:54 PM Viraj Jasani <[email protected]> wrote: > +1 for EOLing 4.x and 4.16. > > > On Thu, 14 Apr 2022 at 3:35 AM, Geoffrey Jacoby <[email protected]> > wrote: > > > Phoenix 4.x is based on HBase 1.x. While a patch release (HBase 1.7.1) > was > > released in July 2021, there's not much active development of it and the > > HBase community is currently debating whether to EOL it. (Though there > > appears to be some interest in releasing 1.7.2.) [1] > > > > HBase 1.x also depends on Java 1.7, which has been out of public support > > since 2015, and the requirement to make 4.x code compatible with Java 1.7 > > is of course a big inconvenience. > > > > In May 2021 there was a previous thread [2] about EOLing the 4.x and 4.16 > > lines which generated a mostly positive response, but was inconclusive > > because of questions of whether Salesforce contributors were going to > want > > the 4.x line to continue. (And most of us Salesforce contributors were > > silent at the time because we didn't really know the answer. :-) ) > > > > I've asked around a lot internally over the past month or two, and the > > consensus here seems to be that we're OK with upgrading to 5.2 to get any > > post-4.16.x features or any bug fixes that are only in 4.x and master > > branches. (If I missed anyone, please speak up!) > > > > Is there interest in the community in keeping the 4.x or 4.16 line going > > (which would probably mean someone stepping forward to RM a 4.17 or > > 4.16.2), or should we EOL them? > > > > Thanks, > > > > Geoffrey Jacoby > > > > [1] https://lists.apache.org/thread/8qy2lqtdwzc10tqnfdhrqvo35z6vkrvk > > [2] https://lists.apache.org/thread/47zbm6bz6gmk16kddj5ptp97w31p2wf8 > > > -- *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/> ------------------------------
