It should be fine to just cut 6.2.0 off and reelase it with Spring 6.2 and Jetty 12 and probably makes sense to do that. Jetty 12.1 just came out but we should stick to Jetty 12.0.x for now I think.
We are not limited on releases so if there's Jakarta features ready we can do a 6.3.0 at any point, even a month later. On Fri, Sep 5, 2025 at 4:48 AM Colm O hEigeartaigh <[email protected]> wrote: > Hi, > > It's increasingly a problem that the only ActiveMQ classic releases > available use EOL libraries (Spring 6.1, Jetty 11), in terms of running > CVEs in production. I'd like to respectfully request that the focus is on > updating to Jetty 12 and releasing, rather than delaying AMQ 6.2.0 for > other features. I'm happy to help out with dependency updates, testing etc. > > Thanks, > > Colm. > > On 2025/08/08 13:20:20 Matt Pavlovich wrote: > > For 6.2.0 I propose merging the Virtual Thread tech preview feature and > move to Jetty 12. > > > > The Jetty 12 PR is ~80% complete. > > > > Matt Pavlovich > > > > > On Aug 7, 2025, at 5:38 PM, Christopher Shannon < > [email protected]> wrote: > > > > > > JB, > > > > > > Sorry for the delayed response, I think the time frame for a 6.1.8 > release > > > is fine. > > > > > > For 6.2.0 that timeline seems ok assuming it's ready by that date, I > would > > > need to go back and look at the proposals for the new Jakarta > features, but > > > is there any particular one you had in mind to include? > > > > > > On Tue, Jul 29, 2025 at 3:39 AM Jean-Baptiste Onofré <[email protected]> > > > wrote: > > > > > >> Hi everyone, > > >> > > >> I propose: > > >> 1. ActiveMQ Classic 6.1.8 by end of August/beginning of September, as > > >> a maintenance release, containing several fixes and dependency updates > > >> 2. ActiveMQ Classic 6.2.0 by end of October/beginning of November. The > > >> purpose here is to add at least one new feature to support Jakarta > > >> Messaging 3.x. > > >> > > >> Thoughts ? > > >> > > >> In the meantime, I'm working on a prototype for ActiveMQ Classic 7.x, > > >> removing Spring dependency and using service discovery mechanism (for > > >> destination policies, transport connectors, etc). Also I'm resuming > > >> the investigation about replicated KahaDB. > > >> > > >> Thanks > > >> 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 > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > >
