On 01/04/2026 14:11, Christopher Schultz wrote:
Mark,
On 4/1/26 5:49 AM, Mark Thomas wrote:
On 31/03/2026 22:47, Christopher Schultz wrote:
Mark,
On 3/31/26 1:50 PM, Mark Thomas wrote:
Coming back to this. I had an idea.
How about "clarifying" that the 1.3.x EOS announcement applied to
the entire 1.x line and noting that it is very unlikely that there
will be any further 1.2.x releases.
Something like:
Subject: [ANN] End Of Support for Tomcat Native 1.x
The End Of Support announcement for Tomcat Native 1.3.x released on
2026-02-11 announced End Of Support for 1.3.x as 2027-03-31.
The Tomcat team wishes to clarify that the EOS announcement for
1.3.x released on 2026-02-11 applies to all 1.x branches.
EOL for Tomcat Native 1.1.x was announced as 2018-09-30 on 2017-09-21.
There was no specific announcement for 1.2.x but the last 1.2.x
release was 1.2.39 on 2023-10-03.
All currently supported Tomcat versions require at least Tomcat
Native 1.3.4.
No 1.2.x releases are expected between now and 2027-03-31.
Tomcat Native 1.3.x releases will continue as usual until 2027-03-31.
+1
Were you suggesting that the above would be the entire announcement,
or to re-work my originally-proposed announcement to include the above?
My intention was to send it as-is.
I'm happy to re-work my announcement to include everything above. I
do think it needs a *little* more than exactly what you have written
above.
My priority is to get something out sooner rather than later (this week).
I think whatever we send should not look like an EOS announcement for
1.2.x. I think it should look more like an explicit clarification of
what should already be obvious to anyone following the development of
Tomcat Native.
Shall we send this notification at the same time as the 3 other April
releases? Or do you think we should send it earlier? We could send it
today... I'm not sure it matters a what the exact timing is.
I think we should send this ASAP. Do you want to rework your original
announcement or should I just send my version?
Mark
Thanks,
-chris
On 13/02/2026 22:42, Christopher Schultz wrote:
On 2/13/26 1:05 PM, Rémy Maucherat wrote:
On Fri, Feb 13, 2026 at 6:59 PM Mark Thomas <[email protected]> wrote:
On 12/02/2026 22:52, Christopher Schultz wrote:
All,
I have a proposed End of Support announcement.
(I find that turn of phrase odd; I always read EOL although
maybe that
term is being phased out?)
Comments welcome.
Having read the announcement, I'm now not sure of the right way to
handle this.
We did have an announcement for 1.1.x but didn't for 1.2.x
although the
circumstances look to be similar. That is probably on me.
We're allowed to help and make sure everything is done properly, so I
would say this is on us ;)
I think I'd lean more towards approach of:
- the last 1.2.x release was more than 2 years ago
- we should have announced EoS for 1.2.x when 1.3.x was released
(more
than a year ago)
- there are no plans for any further 1.2.x releases
- 1.2.x is effectively EoS now
Not sure I'd state this on the users list but if someone can come up
with a *really* good argument why they can't just upgrade to
1.3.x (and
because we depend on a very old, unsupported version of OpenSSL
is NOT a
good argument) then I'd consider a 1.2.x release. Thinking about
it, it
would likely end up being so similar to 1.3.x that they might as
well
just use 1.3.x. Which I guess means I'd consider and then say no
so...
Which brings me back to some variation of stating "1.2.x is
already EoS
- sorry for no advance notice but no releases for 2+ years should
have
been a hint".
+1
Usually when we have a new minor version, the support for the
previous
one ends, but usually we do make a real announcement.
So I'm kind of hearing both of these:
a. 1.2.x is dead, Jim
b. We should support 1.2.x because we technically forgot to
announce EOS
This is why I settled on the "EoS is same as 1.3.x" because (1) we
didn't announce and (1) it is, in fact, dead. But just in case
someone was really expecting support, we will grudgingly do it, but
only after an impassioned recommendation to migrate to 1.3.x, and
then to 2.0.x immediately thereafter. As a concession to us, I'm
not extending support any farther ... ? :)
I do feel bad announcing "sorry, there is no notice on this one".
At least with 1.3.x, they have a countdown of a year-ish.
-chris
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
