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
