On 10/06/2026 15:14, Rémy Maucherat wrote:
On Wed, Jun 10, 2026 at 3:40 PM Mark Thomas <[email protected]> wrote:
On 10/06/2026 13:30, Rémy Maucherat wrote:
On Wed, Jun 10, 2026 at 12:30 PM <[email protected]> wrote:
This is an automated email from the ASF dual-hosted git repository.
markt-asf pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/main by this push:
new 79cc563af5 Fix potential deadlock on copy
79cc563af5 is described below
commit 79cc563af5e4b0580c2213dfda58675105a79d55
Author: Mark Thomas <[email protected]>
AuthorDate: Wed Jun 10 11:29:02 2026 +0100
Fix potential deadlock on copy
I paused my minor fixes work from code review since you asked, but
when is the next tag going to be so that I can resume ? The longer we
wait, the more likely we get flooded by 1000s of PRs about the same
minor stuff (I fear we'll get flooded anyway ...).
It depends on a) when the Commons Daemon release completes - it is still
a vote short and b) whether we want to delay the tag for a Tomcat Native
release to pick up the latest OpenSSL release.
To repeat what I said on June 3rd
"While I was suggesting a pause in the commits as a result of the code
review, I wasn't suggesting an immediate pause. I think we are probably
OK until the Commons Daemon update is committed as that is the one I am
not sure of the timescale for."
If we want to do a Native release we might want to change that to "pause
the code review commits once the Native update is complete"
All I am looking for is a short period of stability before the tag.
Ok, so how about you post 4-5 days before the expected tag date ?
If only I knew when that was going to be. The Commons Daemon release
vote has been open for more than a week. I'm trying to encourage folks
to vote but I can't force them.
Thoughts on trying to include a Native release as well?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
