Clarification on Tomcat 9.1 Release Timeline and Support Plans
somasani nikhil <[email protected]> Thu, 16 Apr 2026 13:57:58 +0530
| Newsgroups | gmane.comp.jakarta.tomcat.user |
|---|---|
| Message-ID | <CAJwQzESDXnPP0DikfLGxdJtQXkhS7OQtaXK3aYQsrgaFy09a+g@mail.gmail.com> |
Hello Team,
We are currently reviewing our application server roadmap and would
appreciate some clarification around *Tomcat 9.1 release and support plans*.
Based on the information shared in the following article:
https://tomcat.apache.org/tomcat-9.0.x-eos.html
our understanding is that *Tomcat 9.0.x will remain supported through March
2027*, and that there are plans for a *Tomcat 9.1.x* line. To help us plan
accordingly, we would appreciate guidance on the following:
1.
*Availability timeline*
- Is there an approximate availability timeframe for the *first Tomcat
9.1.x release*?
- Will 9.1.x overlap with 9.0.x support for a significant period?
2.
*Upgrade considerations (9.0 → 9.1)*
- Are there any *major behavioral, compatibility, or configuration
changes* that users currently on Tomcat 9.0.x should be aware of when
planning a move to 9.1.x? (Except the fact for "APR/native connectors
for HTTP, HTTPS and AJP will not be available")
- Will 9.1.x remain fully *Java EE / javax‑based*, similar to 9.0.x?
3.
*Support and lifecycle changes*
- Are there any *changes in support terms, maintenance policies, or
lifecycle expectations* between 9.0.x and 9.1.x that users should
factor into long‑term planning?
- Any guidance on recommended upgrade windows or best practices would
be helpful.
For our context, *Tomcat 10.x involves a Jakarta EE–based namespace and
significant structural changes*, which requires notable application‑level
work. As a result, we need to make near‑term decisions on whether to
continue on the 9.x line or plan for a larger migration, and clarity on
9.1.x would greatly help our SPM and release planning.
Any details, references, or forward‑looking guidance you can share would be
highly appreciated.
Thank you for the continued community efforts and for maintaining such a
robust and well‑documented platform.
Regards,
Nikhil