Please take note— several tasks were in the Done column, but stale bot had closed out the PR before it was merged. I moved those back out into the ‘In Review’ section so we don’t mistakenly release thinking they were merged.
> On Jul 16, 2026, at 8:48 AM, Matt Pavlovich <[email protected]> wrote: > > I’ve started reclassifying my features and fixes to 6.4.0 (MessageAudit > performance, GC wildcard destinations, etc) to start getting a real idea on > what is left. > > I am working through the list, but want to call out two items that I should > stay targeted for 6.3.0 > > 1. Jean-Louis’ topic send perf fix (its been open a while) > 2. KahaDB fix when working with dedicated cursors (this is a bug fix) > > Thanks, > Matt > >> On Jul 16, 2026, at 8:20 AM, Matt Pavlovich <[email protected]> wrote: >> >> 1. ActiveMQ Karaf support >> >> => All the most critical dependencies are changing in v6.3.0. I think we >> treat the activemq-osgi bundle as ‘best effort’ in the v6.3.0 release. >> Apache Karaf has some catching up to do for Spring 7 and ActiveMQ <-> Jetty >> 12 wiring anyway. If there are any issues, those can be treated as a bug and >> go into a point release of v6.3.x. >> >> 2. JMS 3.1/2.0 website >> >> => I think we update the webpage to remove the target release column (keep >> the released column) and then provide a link to the GitHub Project(s) pages. >> Tracking items in a backlog is normal, and if a feature gets bumped to a >> different release, that’s just how things go in software. >> >> 3. JMS 3.1/2.0 features >> >> => I think we push receiveBody()/deliveryDelay to v6.4.0. My PR with >> delivery delay is the closest to ship, but there is little value in getting >> that one out as the ActiveMQ scheduler is already has more features. >> >> 4. v6.4.0 in September/October >> >> => Sounds good. With Jetty 12 and Spring 7 in we are largely unblocked on >> major things and can rapidly iterate going forward. >> >> Thanks! >> Matt >> >>> On Jul 16, 2026, at 8:02 AM, Jean-Baptiste Onofré <[email protected]> wrote: >>> >>> That works for me. We just have to be careful to what we communicate to the >>> community. >>> >>> We should not announce any commitment before it’s actually done. >>> >>> I know we have been side tracked with security improvements, etc. >>> >>> I propose to simply remove the target version from the website and update >>> the message to the community when a feature is done. >>> >>> Regards >>> JB >>> >>> Le jeu. 16 juil. 2026 à 14:57, Christopher Shannon < >>> [email protected]> a écrit : >>> >>>> Hi JB, >>>> >>>> So to be honest, I don't remember the state that stuff is in because >>>> essentially the only thing anyone has worked on the last few months is >>>> security fixes because of all the AI generated reports (just like the >>>> rest of the open source world). The schedule was created before all of >>>> that hit so I think we will need to adjust it. >>>> >>>> I've been thinking about it and I think at this point my preference is >>>> to not put anything else into 6.3.0 and just focus on testing and >>>> making sure what's there is good for release. I think we can just >>>> update the release notes and schedule and let people know that 6.3.0 >>>> focuses on Jetty 12 and Spring upgrades and 6.4.0, 6.5.0 etc will >>>> resume adding features for Jakarta messaging. >>>> >>>> We could probably target a September/October time frame (a lot of >>>> people have time off in August) for a 6.4.0 release and that can focus >>>> on some new features such as ReceieBody and DeliveryDelay >>>> >>>> Chris >>>> >>>> On Thu, Jul 16, 2026 at 7:47 AM Jean-Baptiste Onofré <[email protected]> >>>> wrote: >>>>> >>>>> Hi >>>>> >>>>> It sounds good to me, and it was the plan (remember the discussion >>>>> about regular release pace). >>>>> However, OSGi support is currently broken and needs a fix. I will >>>>> implement a fix for that very soon. >>>>> >>>>> I would suggest that we include at least one new JMS 3 feature: maybe, >>>>> if we have time, we should review >>>>> https://github.com/apache/activemq/pull/1543 (I think it's in a good >>>>> shape but needs reviews). >>>>> >>>>> In the JMS 3 support >>>>> (https://activemq.apache.org/components/classic/documentation/jms2), >>>>> we said that 6.3.0 should contain: >>>>> - DeliveryDelay: we have an issue about that but no work started. I >>>>> suggest updating the page/issue to 6.4.0. >>>>> - ReceiveBody: it's planned for 6.4.0, but I started. I'm fine to keep >>>>> 6.4.0 as target, but worth to consider for 6.3.0. >>>>> >>>>> So, >>>>> 1. Agree for 6.3.0 next week >>>>> 2. I will update the JMS3 support page >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> On Thu, Jul 16, 2026 at 1:05 AM Matt Pavlovich <[email protected]> >>>> wrote: >>>>>> >>>>>> Hey all- >>>>>> >>>>>> With the Jetty 12 migration complete and merged, we are unblocked to >>>> start winding down the change set for v6.3.0 release. >>>>>> >>>>>> Highlights: >>>>>> Jakarta EE 11 alignment >>>>>> Jetty 12 >>>>>> Spring 7 >>>>>> Virtual Threads >>>>>> .. a large pile of other features and fixes >>>>>> >>>>>> Please have all feature changes in by the end of the week, so we can >>>> start finalizing reviews and merges. >>>>>> >>>>>> This is a big one, so we’ll need a bit more time to ensure >>>> documentation and review. >>>>>> >>>>>> Thanks! >>>>>> Matt Pavlovich >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> 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 >>>> >>>> >>>> >> >> >> --------------------------------------------------------------------- >> 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
