Hi Matt, The current scope for 6.4.0 looks good to me, and I agree with calling a feature freeze. Let's focus on finishing up the items currently in review and in progress. Any new features can go into 6.5.0, which we can release shortly after.
Regards, JB On Fri, Sep 11, 2026 at 9:36 PM Matt Pavlovich <[email protected]> wrote: > > Thoughts on calling for a feature freeze on adding any *new features* for the > v6.4.0 project to give us time to focus on closing down the exciting features > we have in there right now. I expect there to be some more back-and-forth in > the review cycle. > > Also— not suggesting everything in the 6.4.0 is confirmed to be “in” for the > release. Somethings may need to slide to v6.5.0 or v6.6.0— but don’t fret, > it doesn’t mean it’ll be a long way out— we have a good cadence going! > > Of course, bugs and security fixes can always be considered as needed. > > v6.4.0 Project stats: > > Done: 50 items > In Review: 17 > In Progress: 6 > Ready: 3 > Backlog: 6 > > ref: https://github.com/orgs/apache/projects/624 > > Thanks, > Matt Pavlovich > > > On Sep 9, 2026, at 9:33 AM, Matt Pavlovich <[email protected]> wrote: > > > > Sound good, tag them with the Project and I’ll help make a review pass. > > > >> On Sep 9, 2026, at 7:35 AM, Jean-Baptiste Onofré <[email protected]> wrote: > >> > >> Hi > >> > >> I have a couple of PRs (fixes) to include on both 6.4.x and 6.3.x. > >> > >> Regards > >> JB > >> > >> On Tue, Sep 8, 2026 at 9:42 PM Christopher Shannon > >> <[email protected]> wrote: > >>> > >>> 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 > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> 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
