Hi JB- Sounds good. If no one else has any other thoughts, we’ll move forward with this plan starting tomorrow (Friday).
Steps: 1. Merge any outstanding 6.3.x dependency PRs that are open (don’t leave any 1/2 merged updates like Jackson libraries) 2. Remove 6.3.x branch from dependabot workflow 3. Close the v6.3.4 project on GitHub Thanks, Matt > On Nov 11, 2026, at 10:32 PM, Jean-Baptiste Onofré <[email protected]> wrote: > > +1 > > The plan when moving forward on minor (6.3.x, 6.4.x, ...) was about new > features added to JMS spec. > 6.4.x includes receiveBody(). > > So, there's need to maintain 6.2.x/6.3.x any longer. > > +1 > > Regards > JB > > On Wed, Nov 11, 2026 at 11:32 PM Matt Pavlovich via dev > <[email protected] <mailto:[email protected]>> wrote: >> Reviewing differences between v6.4.x and v6.3.x and there are zero changes >> to major dependencies. >> >> With 6.5.0 underway, I’m thinking we do not need to continue v6.3.x, as >> v6.4.0 is the natural upgrade path and adds a number of new security >> features which we would want to encourage users to have around in order to >> be able to enable them as needed. >> >> Dependencies aligned (v6.4.0 and v6.3.3) >> JMS API: 3.1.0 >> Jetty 12.1.12 >> Spring 7.0.9 >> Jackson 2.22.4 >> Log4j2 2.26.1 >> SLF4J 2.0.20 >> Jakarta Servlet 6.1.0 >> Java runtime 17 >> >> Thoughts on declaring v6.3.x inactive alongside the v6.5.0 release? >> >> Thanks, >> Matt >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> <mailto:[email protected]> >> For additional commands, e-mail: [email protected] >> <mailto:[email protected]> >> For further information, visit: https://activemq.apache.org/contact >> >>
