I agree with all the thoughts and prioritization on Jakarta support. The intent here is to not create a prioritization list, but rather a categorization.
The intent of creating Milestones would be to organize what has been announced on dev lists and allow for across-version tracking of issues and PRs that apply to a Milestone. For example, Jakarta 3.1 has multiple issues tagged across multiple versions. -Matt > On Sep 15, 2026, at 1:50 PM, Jean-Louis Monteiro <[email protected]> > wrote: > > Hi > > Same here, I think Jakarta Messaging 3 is the priority for me. > > I ran the TCK the other day and we are not too far even though from > experience the last few failures are harder and longer to fix. > I will pull again my PR and see if I can finish the async one. > > Jean-Louis > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Sep 15, 2026 at 7:05 PM Jean-Baptiste Onofré <[email protected]> > wrote: > >> Hi Matt and Chris, >> >> As previously discussed, our top priority should be full Jakarta >> Messaging 3.1 support. I believe this needs to be our main focus, with >> other items addressed on a best-effort basis. >> >> Beyond that, here is how I would prioritize the remaining items: >> >> 1. OAuth support: Close to being merged. >> 2. OpenTelemetry support: Also close to being merged (specifically >> pure OTLP, rather than Prometheus). >> 3. Replicated KahaDB and runtime modernization: Both require >> significant effort. While PoCs have started, they still need extensive >> testing and community consensus. >> >> On a personal note, after using both for a few months, I still prefer >> GitHub Milestones over Projects. >> >> Regards, >> JB >> >> On Tue, Sep 15, 2026 at 4:24 PM Matt Pavlovich <[email protected]> >> wrote: >>> >>> Playing around with how GH Milestones and Projects can provide >> visibility into planning and roadmap-ish type things for the community. >>> >>> We have a lot of great ideas in various stages from ‘heads up’ -> Issues >> -> PRs and tagging those with a Milestone would be helpful in organization >> and discovery. >>> >>> Currently playing around with these ideas: >>> >>> - Jakarta 3.1/JMS 2.0 support (already exists) >>> - 2026 Modernization (project modernization, new language features, >> refactoring deprecated language usage — ie use Long.valueOf v new Long(), >> etc) >>> - OAuth support (mailing list announced, issue and PR) >>> - Replicated KahaDB (mailing list announced) >>> >>> Thoughts? >>> --------------------------------------------------------------------- >>> 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
