Ok looks like we have consensus on raising the baseline. I am also fine to directly move to 21, if no one objects.
Actually, I would suggest, that we run the next release with Java 11 to get out the open fixes and dependency updates, formally announce the switch to a new Java baseline version for the next release and do the switch. Perhaps, it would be good to receive some community feedback too. I will write a small notice to user@ Gruß Richard > Am 08.11.2024 um 19:24 schrieb Rui Abreu <rui.ab...@gmail.com>: > > I concur > +1 (binding) > > Cheers folks > > On Fri, 8 Nov 2024 at 16:40, Julien Nioche > <lists.digitalpeb...@gmail.com> wrote: >> >> +1 for either 17 or 21 >> >> Julien >> >> On Fri, 8 Nov 2024 at 13:23, Alexandre Vermeerbergen < >> avermeerber...@gmail.com> wrote: >> >>> +1 (binding) even if I would love a bigger jump, i.e., to JDK 21 so as to >>> open the road to the use of virtual threads for executors ! >>> >>> Thanks, >>> Alexandre >>> >>> Le ven. 8 nov. 2024, 11:03, Richard Zowalla <r...@apache.org> a écrit : >>> >>>> Hello everyone, >>>> >>>> As we continue to develop Apache Storm, maintaining compatibility with >>>> newer versions of Java is essential to take advantage of the performance, >>>> security, and feature improvements in the Java ecosystem. >>>> The current minimum Java version supported for Apache Storm development >>> is >>>> outdated and can limit our ability to take advantage of more modern >>>> language features, libraries, and JVM enhancements. >>>> >>>> Therefore, I am proposing to raise the minimum Java baseline for >>>> development to Java 17. This will allow us to keep pace with other major >>>> frameworks (Spring, etc.) and pave the way for upgrading AMQ (JMS) >>>> integration. >>>> >>>> Java 17 introduces many benefits, including improved garbage collection, >>>> improved performance, new language features (such as pattern matching and >>>> records), and a stronger security model. >>>> >>>> By making Java 17 the baseline for development, we will be able to >>>> integrate these benefits into the codebase, streamlining dependencies, >>>> reducing CI/build times and compatibility complexities. >>>> >>>> WDYT? >>>> >>>> Gruß >>>> Richard >>> >> >> >> -- >> *Julien Nioche * >> >> >> digitalpebble.com <http://www.digitalpebble.com/>
