On 16/06/2026 02:16, Jarugubilli Bharadwaj via dev wrote:
Confidential - Oracle Restricted \Including External Recipients

Good luck with that - this is a public mailing list.

Hello Apache Tomcat Developers,

I hope you are doing well.

I am writing to enquire about the planned Apache Tomcat 9.1.x codebase. I saw 
on the Tomcat version page that extended support for Tomcat 9 is expected to 
continue through a future 9.1.x branch, which will be started when Tomcat 9.0.x 
reaches end of support.

Could you please confirm when the Tomcat 9.1.x source code branch is expected 
to be published?

Given the minimal differences between what will be the final 9.0.x release and the start of the 9.1.x branch, I expect the 9.1.x branch to be created from the final 9.0.x tag - so late March 2027, early April 2027.

We might create 9.1.x earlier than that and run the two branches in parallel until 9.0.x reaches end of support but I don't really see the point. 9.1.x is just 9.0.x with the following changes:
- no APR/Native connectors
- no Tomcat Native 1.3.x support

You can effectively run any 9.0.x release as if it were 9.1.x just by not using the APR/Native connectors and using Tomcat Native 2.0.x (or FFM) if you want OpenSSL integration. I'd strongly encourage anyone planning to use 9.1.x to start doing that now. Then the 9.0.x to 9.1.x switch over will be no different to a normal point release update.

Also, should we monitor the existing Apache Tomcat GitHub repository for this 
branch?

https://github.com/apache/tomcat

Yes.

At present, I can see the public branches such as main, 11.0.x, 10.1.x, and 
9.0.x, but I do not see a 9.1.x branch yet.

Please let us know whether early Tomcat 9.1.x development will be published in 
the same repository as a 9.1.x branch, or whether there is another public 
repository or branch that we should follow.

There is no other repository.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to