Out of curiosity, what's the rationale for continuing releases for 6.1.x? You already indicated that 6.1.x has had new features that probably should have been on 6.2.x.
Also, there's been no more releases for 6.0.x since 6.1.0 was released. How is the situation now with 6.1.x & 6.2.x different from the situation with 6.0.x & 6.1.x previously? Justin On Thu, Oct 31, 2024 at 11:24 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Yes, 6.1.4 will be submitted to vote just with fixes and updates. > > 6.2.0 will be prepared in parallel for JMS2/Jakarta JMS3 features. > > Regards > JB > > On Thu, Oct 31, 2024 at 4:35 PM Jamie G. <jamie.goody...@gmail.com> wrote: > > > > So a 6.1.4 of bug fixes will RC as well? > > > > On Thu, Oct 31, 2024 at 1:03 PM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > > > > We already included new JMS2/Jakarta3 features on 6.1.x in the past. > > > > > > But I think you are right Justin, I think it makes sense to jump to > > > 6.2.0 and include new JMS features in 6.3.0, 6.4.0, etc. > > > > > > So, to summarize: > > > - let's prepare 6.2.0 including AMQ-8464 and AMQ-8320 > > > - let's schedule AMQ-8324 and AMQ-8323 in 6.3.0, 6.4.0, etc > > > > > > It would be great to target JMS2/Jakarta JMS3 completed for 6.5.0 > (best effort). > > > > > > Regards > > > JB > > > > > > > > > On Thu, Oct 31, 2024 at 4:21 PM Justin Bertram <jbert...@apache.org> > wrote: > > > > > > > > Wouldn't new functionality like this make more sense in a minor > release > > > > (i.e. 6.2.0) rather than a micro release (i.e. 6.1.4)? Micro > releases are > > > > typically for bug fixes and maybe some trivial improvements. I > believe Matt > > > > made this same point when discussing 6.1.4 last month [1]. > > > > > > > > > > > > Justin > > > > > > > > [1] https://lists.apache.org/thread/spj8fm567367qy0w3q98oombss64ok6q > > > > > > > > On Thu, Oct 31, 2024 at 10:10 AM Jean-Baptiste Onofré < > j...@nanthrax.net> > > > > wrote: > > > > > > > > > Hi folks, > > > > > > > > > > I'm starting the preparation of the ActiveMQ Classic 6.1.4 release. > > > > > > > > > > In addition to the improvements and bug fixes, I propose to move > > > > > forward on the full JMS 2/Jakarta 3 support. > > > > > > > > > > I propose to include two additional JMS2 features in 6.1.4: > > > > > - support of JMSConsumer.readBody(Class) > > > > > (https://issues.apache.org/jira/browse/AMQ-8464). I'm resuming > work on > > > > > this one. > > > > > - support for JMSProducer deliveryDelay > > > > > (https://issues.apache.org/jira/browse/AMQ-8320). Matt is working > on > > > > > it. > > > > > > > > > > We will be able to focus on producer CompletionListener (AMQ-8324) > and > > > > > Shared Topic Consumers (AMQ-8323) features in 6.1.5, 6.1.6, 6.1.7. > > > > > > > > > > I think it makes sense to take the time to complete AMQ-8464 and > > > > > AMQ-8320 for 6.1.4. > > > > > > > > > > Thoughts ? > > > > > > > > > > Regards > > > > > JB > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > > > > > For additional commands, e-mail: dev-h...@activemq.apache.org > > > > > For further information, visit: > https://activemq.apache.org/contact > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > > > For additional commands, e-mail: dev-h...@activemq.apache.org > > > For further information, visit: https://activemq.apache.org/contact > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > > For additional commands, e-mail: dev-h...@activemq.apache.org > > For further information, visit: https://activemq.apache.org/contact > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > For additional commands, e-mail: dev-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > > >
