Good point, let me do that. Thanks !
Regards JB On Fri, Jan 23, 2026 at 8:27 AM Colm O hEigeartaigh <[email protected]> wrote: > +1, but a minor suggestion is to backport to Log4J upgrade to 5.19.x > to fix CVE-2025-68161. > > Colm. > > On Thu, Jan 22, 2026 at 4:07 AM Matt Pavlovich <[email protected]> > wrote: > > > > Sounds good! I have one or two small changes for v5.19.2 > > > > I think v6.2.1 should be close to ready and no new features. > > > > Thanks! > > > > > On Jan 16, 2026, at 10:44 PM, Jean-Baptiste Onofré <[email protected]> > wrote: > > > > > > Hi everyone, > > > > > > As discussed a few weeks ago, I propose moving forward with the > ActiveMQ > > > 5.19.2 and 6.2.1 releases to maintain our regular release pace. > > > > > > I would like to use these releases as a milestone for our transition to > > > GitHub Issues. I am currently performing the triage on Jira to > facilitate > > > this. > > > > > > Please let me know if there are any objections. > > > > > > Regards, > > > JB > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > For further information, visit: https://activemq.apache.org/contact > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > >
