My PR that I pushed up over a month ago for index truncation I wanted to get in as well into 6.4.0
It's just been waiting for a review Chris On Mon, Sep 7, 2026 at 10:23 AM Jean-Baptiste Onofré <[email protected]> wrote: > > It sounds great to me! > > Let's rock :) > > Regards > JB > > On Mon, Sep 7, 2026 at 4:06 PM Matt Pavlovich <[email protected]> wrote: > > > > I have a PR for Jakarta 3.1/2.0 pool support that I think is ready for > > review and would be a good addition to the 6.4.0 release. > > > > That sounds good — I made a pass at pruning and sliding other issues and > > PRs to 6.5.0. Even after the first pass of pruning, we are sitting on over > > 15+ open items and some of those will have heavy review-rework cycles. I > > think we’ll need to push out several other items and get that list under 10 > > to realistically make the timeframe. > > > > Current v6.4.0 highlights: > > > > 1. JMS 3.1 receiveBody, activemq-pool > > 2. SSL modernization > > 3. ClientId authorization > > 4. Many other fixes and performance improvements > > > > -Matt Pavlovich > > > > > On Sep 6, 2026, at 1:54 AM, Jean-Baptiste Onofré <[email protected]> > > > wrote: > > > > > > Hi > > > > > > I agree. > > > As said on Slack, I'm volunteering for the 6.4.0 release. > > > > > > Instead of next week, I would propose the week after, simply because > > > we need to include a few new features (receiveBody for instance is > > > close imho). > > > > > > The purpose to have new 6.x "branch" is to include new Jakarta > > > Messaging 3 features, so, with receiveBody at least, we are good for > > > 6.4.0 imho. > > > > > > Regards > > > JB > > > > > > > > > On Sat, Sep 5, 2026 at 7:59 PM Matt Pavlovich <[email protected]> wrote: > > >> > > >> A couple patches came in mid-cycle of the releases this week. > > >> > > >> I took a peak at the v6.4.0 project and saw it already had 46 completed > > >> issues and PRs. I think we should consider releasing v6.4.0 next instead > > >> of a v6.3.x patch. > > >> > > >> Thoughts? > > >> > > >> 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
