Hi Tim, I think jumping to Java 17 would be a bit much for 3.x.
I would vote for a shorter EOL for Tika 2.x What I’ve seen is that users who are forced to continue using older versions of Java are generally able to back port changes they need, once support is EOL. So if there’s a critical bug fix in 3.x in 9 months, anyone still on Java 8 would be able to fork/fix it themselves, without relying on the (small, over-loaded) Tika community to keep Java 8 actively supported. — Ken > On Sep 13, 2023, at 12:26 PM, Tim Allison <talli...@apache.org> wrote: > > We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one > more year. I've started the branches and started making some changes in this > direction. > > Is it worth pushing this modernization further or faster, with either: > a) Jump to Java 17 now and keep Java 8 in 2.x for one more year > b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say > 6 months or fewer? > > Thank you, all, for your feedback! > > Best, > > Tim > > -------------------------- Ken Krugler http://www.scaleunlimited.com Custom big data solutions Flink, Pinot, Solr, Elasticsearch
