As far as stability and "robustness" goes ActiveMQ Artemis is already production ready (and has been for a long time). The timeline for becoming ActiveMQ 6 is based on sufficient feature parity with the 5.x code-base, not general stability or production readiness. Lots of users have deployed Artemis to production.
There's no specific timeline set, although a lot of work has been done over the last year to close the feature gap. It would probably be a good idea for the community to reassess the situation and clarify what's still lacking (if anything). Justin On Mon, Aug 31, 2020 at 12:15 PM Weihao Li <w...@aware.com> wrote: > Hi, > > Thank you for your information. We are not looking for any specific > feature. We want to make sure if ActiveMQ Artemis is stable and robust > enough for migration. As your guys mentioned on official website, once > Artemis reaches a sufficient level, it will become ActiveMQ 6. Thus, do you > have a timeline that Artemis becomes to ActiveMQ 6? > > Thanks, > Weihao Li > > From: Weihao Li > Sent: Wednesday, August 26, 2020 10:02 AM > To: 'users@activemq.apache.org' <users@activemq.apache.org> > Subject: ActiveMQ Artemis Roadmap > > Hi, > > Sorry if this is not the correct mailing list. > > We are loyal Active MQ users for many years and we notice ActiveMQ Artemis > is released and we plan to migrate ActiveMQ 5 to ActiveMQ Artemis in the > future. But seems like ActiveMQ Artemis haven't reached the sufficient > level of feature with the 5.x code-base. Thus, we want to get some > information about the roadmap of ActiveMQ Artemis so that we can schedule > the migration work. > > Thanks, > Weihao Li > Senior Software Engineer Aware, Inc. > > w...@aware.com<mailto:w...@aware.com> > P. 781.687.0478 > > 40 Middlesex Turnpike > Bedford, MA 01730 > Main. 781-276-4000 > www.aware.com<http://www.aware.com/> > Connect with Aware: > Web<https://www.aware.com/> | Blog<https://www.aware.com/blog/> | Twitter< > https://twitter.com/awarebiometrics> | LinkedIn< > https://www.linkedin.com/company/aware-inc.> > >
