Previously in various contexts - specifically, I am thinking of a Hadoop JIRA where we once had a conversation on this topic, but I believe there have been others - you have declared 3.5 a long term stable (LTS) release.
A sudden EOL of an LTS is jarring and makes future promise of LTS untrustworthy. What I would recommend for what it’s worth is a timetable to EOL of 3.5 that is reasonably long, like one or two years, should you decide to EOL it. > On Jan 30, 2022, at 5:00 AM, Enrico Olivelli <eolive...@gmail.com> wrote: > > Hello, > We are going to release 3.8.0. > It is time to think about moving 3.5 to EOL. > > Key points: > - we already have a few other "active" branches, 3.6 and 3.7 > - 3.5 still has "ant" files, and cherry picking libraries upgrade is > awkward (you always have to create a separate patch) > - moving to 3.6 is quite easy, so people should not be stuck if > requested to upgrade to 3.6 > > Thoughts ? > > > Enrico
