On Wed, Jun 17, 2026 at 10:47 PM Mark Thomas <[email protected]> wrote: > > On 05/06/2026 08:25, Mark Thomas wrote: > > On 05/06/2026 07:52, Rainer Jung wrote: > >> Am 29.05.26 um 18:19 schrieb Mark Thomas: > >>> All, > >>> > >>> The good news is that the new Daemon release is available and the > >>> release branches have all been updated. > >>> > >>> Unfortunately, we are going to need another migration tool release > >>> too. I am about to start that vote. > >>> > >>> Other than that I still have a handful of things I want to (try and) > >>> get fixed before the June tag so I don't think I am going to be in a > >>> position to tag before the middle of next week. > >>> > >>> My suggestion is that we re-assess where we are in terms of being > >>> ready to tag once the migration tool update is complete. > >> > >> I took the heads of 11.0.x, 10.1.x and 9.0.x from yesterday afternoon > >> and let some of my test zoo combinations run against them (especially > >> various Java and OpenSSL versions). No new test failures, only the > >> very sporadic ones, that are not regressions. I missed Rémy`s evening > >> fix for RewriteValve though. > > > > Thanks. That is good to hear. > > > > The migration tool update is complete but the Commons Daemon 1.6.1 vote > > has not yet passed. I'd encourage anyone who is a Commons PMC member to > > test the release and vote. > > > > I'm mostly done with my TODO list for the June releases. I have a few > > non-urgent Tomcat things from $dayjob that I am going to look while > > waiting for the Daemon release to finish. > > > > I think we'll be ready to tag as soon as the Daemon version is updated. > > If anyone has anything else they want to get into the June releases now > > would be the time to speak up. > > Finally. > > I am just running the unit tests across Linux, Windows and MacOS to > confirm everything is passing and then I intend to tag 11.0.x. Assuming > there are no last minute failures, I should be in a position to tag in > the next few hours.
+1 Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
