Full Jakarta support should likely be the most important thing, besides security fixes. I think stuff like OAuth is fine to work on but shouldn't be taking precedence over getting fully spec compliant or fixing security reports.
I would not be messing around with stuff like replicated KahaDB until we have shared subscription support as that will require changes. I'm also working on index compaction (and have a todo for pushing up journal compaction) which is going to require major refactoring. Chris On Tue, Sep 15, 2026 at 10:24 AM 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
