The more releases the merrier. Personally though I would stop short of generally advertising a cadence, since results seem to forever miss such guidance, and instead just aim to actually do it. ETAs on the website are regularly wrong, e.g the site is wrong right now (either dates in the past, or recently updated too far in the future) and has been up to and over a year out at times.
On Tue, 11 Nov 2025 at 16:08, Jean-Baptiste Onofré <[email protected]> wrote: > > Hi folks, > > In order to ship changes faster (I'm thinking of the discussion about > VirtualThread in Classic 6.2.0 for instance), and to have a > "predictable" cycle for our users, I would like to propose a monthly > release pace for ActiveMQ Classic. > > For instance, it means that 6.3.0 can be released in December, 6.4.0 > in January, etc. > > The purpose is also to encourage contributors as their contributions > will be included in releases faster. > I also think that it would be a good way to be up to date with > dependencies (I'm thinking of the discussion about a bunch of Jira > regarding dependency updates in Classic 6.2.0). > > Thoughts? > > Regards > JB > > --------------------------------------------------------------------- > 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
