Re: Apache Tomcat 9.1.x release timeframe

17 Jul 2026 20:34:54 Lisa Sayre <[email protected]>:

> Mark,
> Thank you for the information.
>
> I have read the additional links, and I would like to ensure I=20
> understand the release timeline for 9.1 as I'm a bit confused.
> Additional links that were provided and that I read:
> https://tomcat.apache.org/tomcat-9.0.x-eos.html
> https://lists.apache.org/thread/71ymfh35x8fnz7pnm6cylmkwsyblto97
>
> From these links I gather:
> 1. Support for Apache Tomcat 9.0.x will end on March 31st, 2027.
> 2. Final release of 9.0.x will be made shortly before March 31st.
> 3. Shortly before 9.0.x support ends on March 31st,=C2=A0 releases from a=
=20
> new 9.1.x branch will be made available.=C2=A0=C2=A0 Therefore, it will n=
ot be=20
> April.
> 4. Support for 9.1 including security vulnerability fixes for 9.1 will=20
> continue until December 31st, 2030.
> 5. There will be no security vulnerability fixes in 9.0 after the 9.1=20
> release is made available.
>
> Are all the points above, correct?

1. Yes
2. Probably more like early to mid-March which may or may not match=20
"shortly before" depending on how that phrase is read.
3. Releases are relatively easy but do require some (volunteer) effort.=20
It is arguable there is no need for an overlap and 9.1.x can just follow=20
9.0.x.=C2=A0 At this point I'd say the most likely scenario is the first 9.=
1.x=20
release will happen at the same time as the last 9.0.x release given what=
=20
we have previously said. That also mitigates most of the concerns raised=20
around the "gap" between 9.0.x and 9.1.x. I remain unconvinced it is=20
strictly necessary but it does look to be expedient.
4. At least. We'll see how things go. An extension isn't impossible.
5. Yes, assuming releases as per the above.


> We are not using the APR/native connector - and therefore anticipate we=
=20
> just need to advise our customers to upgrade to 9.1 in the development=20
> and production environments.
> We would like to test this before we provide this guidance to our=20
> customer base.

In which case the move to 9.1.x should be no different to a 9.0.x update.

> Can we get any information regarding how much time there will be=20
> between the final drop of 9.0.x and the new 9.1. release in March?

See above.

Mark


> This will help us understand how much time we will be able to=20
> internally test the 9.1 release before we need to provide it to our=20
> customers before March 31st when 9.0 is EOL.
> We anticipate we will only need a day or two to drop it in and run our=20
> automation test suite to ensure everything is okay.
> The key for us is to be able to do this before March 31st, and also=20
> give our customers some time to install before March 31st and 9.0 goes=20
> EOL.
>
> Thank you for your time!
> Lisa
>
>
>
> Lisa Sayre
> VP R&D DDI
> =C2=A0=C2=A0+1 (610) 822-2396
> =C2=A0=C2=A0cygnalabs.com
>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
> This electronic message contains information from Cygna Labs Corp.,=20
> which may be privileged or confidential.=C2=A0The information is intended=
=20
> for use only by the individual(s) or entity named above. If you are not=
=20
> the intended recipient,=C2=A0please notify the sender immediately by e-ma=
il=20
> and be aware that any disclosure, copying, distribution or use of=20
> the=C2=A0contents of this e-mail is strictly prohibited. Cygna Labs monit=
ors=20
> its e-mail system and may record your e-mails. Cygna Labs Corp, 1111=20
> Lincoln Rd., Suite 760, Miami Beach, FL 33139
> =C2=A0
>
> -----Original Message-----
> From: Mark Thomas <[email protected]>
> Sent: Friday, July 17, 2026 11:26 AM
> To: Tomcat Users List <[email protected]>
> Subject: Re: Apache Tomcat 9.1.x release timeframe
>
> 17 Jul 2026 16:57:16 Eddie Rowe via users <[email protected]>:
>
>> The helpful links posted again indicate there will be a "few weeks" of
>> overlap between the release of 9.1 and the EOL of 9.0.=C2=A0 Does a "few
>> weeks" mean 2 weeks or does it mean like 8 weeks?=C2=A0 I can appreciate
>> this 9.1 being treated like a normal maintenance release in the 9.0.x
>> series but I don't think there is an appreciation that upgrading to
>> those minor releases can be painful for some of us.=C2=A0 (Ignoring for =
the
>> moment that some are using connectors that are being removed in 9.1
>> which breaks things for us.)=C2=A0 Each release of Tomcat, despite the h=
ard
>> work of several persons, has bugs.=C2=A0 If the first release of 9.1 has=
 a
>> bug that affects someone they might have to stay on 9.0.x and if 9.1
>> corrects a security issue that puts people in a difficult position.
>> And there are going to be more than a few persons who try to upgrade
>> only to learn their AJP connectors no longer work. 8-(
>
> None of the above is any different to any other point release upgrade.
>
> You still have 8 months to stop using the features that will be removed=
=20
> in the 9.0.x to 9.1.x change over.
>
> AJP !=3D APR - they are completely different features. Only the=20
> APR/Native connector is being removed. AJP support will continue.
>
> I don't have a great deal of sympathy for security teams that can't get=
=20
> their head around how this transition will occur and why is should be a=
=20
> complete non-issue but parallel releases of the first 9.1.x and last=20
> 9.0.x releases some time in March 2027 are certainly possible - even=20
> though I continue to be of the view that is unnecessary.
>
> Mark
>
> (Yes, the exact details of how this will work have evolved over time=20
> but the aim remains the same, the smoothest possible transfer from=20
> 9.0.x to 9.1.x for those users who still haven't made the transition=20
> from Java EE to Jakarta EE)
>
>>
>>
>>
>> -----Original Message-----
>>> I think Mark just confused the dates. According to the official
>>
>>> documentation (https://tomcat.apache.org/tomcat-9.0.x-eos.html) and
>>> Mark
>>
>>> himself
>>
>>> (https://lists.apache.org/thread/71ymfh35x8fnz7pnm6cylmkwsyblto97),
>>
>>> there will be a 9.1.x release before 9.0.x is EOL.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]