On Fri, Jul 12, 2024 at 1:04 PM Dimitris Soumis <dsou...@redhat.com> wrote: > > Hello, > > Regarding the end-of-life date for Tomcat 9.0.x, you can find the relevant > information in this link, which contains an email from the mailing list: End > of Lifecycle for Tomcat 9.0.x > <https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0>. > > As for the necessity of upgrading to Tomcat 10.1.x from 9.0.x, please note > that there are no immediate security concerns, as Tomcat 9 continues to > receive all necessary fixes for new CVEs. However, upgrading to Tomcat > 10.1.x allows you to take advantage of the latest standards and APIs with > Jakarta EE 10 specification support. This can be beneficial for staying > up-to-date with current technologies and potentially improving performance > and compatibility with other modern applications and frameworks.
Most likely some users will never be able to migrate to jakarta.*. We know it, so the Tomcat 9.x EOL is a long time away. Maybe 10.1 gets EOLed before since there's no incentive for not EOLing this one according to the usual schedule. I just ported the OpenSSL FFM support to 9.0, which was a big missing feature compared to 10.1 and 11. This sort of porting likely extends the usefulness of 9.0. Also keeping branches closer helps long term maintenance. As for 9.12 (.x is supposed to match the corresponding major version; since we do not need a .x now, it means it's not going to be .10, and .11 seems unlikely as well since we are likely ok for the next 2-3 years), the rationale would be: - Drop the APR connector. - Bump the base Java version to at least 17 (likely 21 or 25). The Java 8 release target is a long term problem since it looks like Java 25 will not have it (Java 22 has now started showing removal warnings). Developers will thus have to use Java 21 to build Tomcat 9.0. The flexibility of Ant seems to allow navigating everything relatively easily however. - Bump dependencies. Thankfully no runtime related dependencies that we cannot maintain ourselves so this is likely not critical. - Sync APIs with the corresponding .x to ease maintenance. Most likely this last one would cause issues. At this point 9.12 does not look inevitable to me. We'll see ! Rémy > Best regards, > > Dimitris > > On Fri, Jul 12, 2024 at 1:41 PM Sai Charan Teja Pratti > <sai-charan-teja.pra...@broadcom.com.invalid> wrote: > > > Hi, > > > > Can you please share the end of lifecycle date for tomcat 9.x. > > Also, please share the necessity of upgrading tomcat to 10.1.x from 9.x > > > > Thanks, > > Sai > > > > This electronic communication and the information and any files > > transmitted with it, or attached to it, are confidential and are intended > > solely for the use of the individual or entity to whom it is addressed and > > may contain information that is confidential, legally privileged, protected > > by privacy laws, or otherwise restricted from disclosure to anyone else. If > > you are not the intended recipient or the person responsible for delivering > > the e-mail to the intended recipient, you are hereby notified that any use, > > copying, distributing, dissemination, forwarding, printing, or copying of > > this e-mail is strictly prohibited. If you received this e-mail in error, > > please return the e-mail to the sender, delete it from your computer, and > > destroy any printed copy of it. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
