Mark,
On 12/12/25 5:40 AM, Mark Thomas wrote:
On 10/12/2025 20:11, Rémy Maucherat wrote:
On Wed, Dec 10, 2025 at 6:24 PM Mark Thomas <[email protected]> wrote:
<snip/>
My plan is to commit the changes to Tomcat Native, produce 2.0.x and
1.3.x releases and then commit the changes to Tomcat. There might be a
few early changes to Tomcat to account for new OCSP functionality else
we may start to see CI failures as we test latest Tomcat code with
latest Tomcat Native code.
+1, I'll definitely look at the code.
Thanks. Another set of eyes on all these changes would be good.
I think the Tomcat Native (2.0.x and 1.3.x) branches are now at at point
where I can tag them. I intend to do that early next week with a view to
completing the releases by the end of next week (hopefully before too
many folks are on holiday).
Tomcat trunk looks to be fine with both 2.0.9 and 2.0.x so the CI system
should be happy as well.
I have a bunch of changes to 12.0.x to apply. I'll apply what I can
before the Tomcat Native releases are complete but some changes depend
on the new Native functionality and will have to wait until the Native
releases are complete. I also need to update the docs for all the new
settings. I'll probably need a few days in early January to get all that
done before the January releases can be tagged.
In your opinion does tcnative have any decent kind of unit-test coverage?
We don't necessarily need to have Java-based unit tests, but even
C-based tests?
I only ask because it would be very handy to be able to perform a quick
smoke-test of a tcnative release on a few platforms without having to
stand-up Tomcat, etc. I know your setup is quite elaborate and it's
fairly "easy" for you to do all of this, but my environment is much more
modest. I'd still like to cast meaningful votes for tcnative, even if
they are compile-and-unit-test votes only.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
