>
> As part of the roadmap discussion, we must also decide if one of the goals
> for Artemis is still to be a drop-in replacement for ActiveMQ. I know that
> at one time this was the goal, i.e., allow current ActiveMQ users to drop
> in Artemis and have everything just continue to work. Is there
Dev list got dropped so adding back in (really this probably only belongs
the dev list anyways)
On Thu, Jul 11, 2019 at 12:08 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> Many of those pull requests are years old. Furthermore no one is saying
> there is no interest in a
Many of those pull requests are years old. Furthermore no one is saying
there is no interest in a project. But there is a huge difference from
supporting 5.x in terms of bug fixes and small features than talking about
doing something like adding new protocols or JMS 2.0 support. For example
the
(Reposting in this roadmap discussion)
I agree that we must define a clear roadmap. We should create a new wiki
page for an overall ActiveMQ project roadmap that includes info for all the
ActiveMQ components (ActiveMQ, ActiveMQ Artemis, ActiveMQ NMS and ActiveMQ
CMS). There is already an ActiveMQ
Its about having clear direction as a project. Im not saying it has to be
artemis im not saying it has to be classic
But there does have to be a single and very clear direction so end users have a
clear understanding in the long term direction.
Having ever changing direction is worse
Hi,
We can a see there is still an interest from the users to Apache
ActiveMQ 5.x.
In github we have 61 open PR => https://github.com/apache/activemq/pulls
Why forcing users to migrate to Artemis if the community is still active?
regards,
François
fpa...@apache.org
Le 08/07/2019 à 18:15,
I think as a project we need to be clear in direction here with one roadmap. To
avoid users confusion.
I was on the understanding that as a community and PMC a roadmap was already
agreed.
And this was for artemis to become activemq 6 was agreed and once it has all
features (and more) of
Hi JB,
I think it make a lot of sense to focus on this points and I will be
more than happy to contribute!
There is a very large community of users around the ActiveMQ 5.x and
it's still very widely use in production environment.
I'm not sure that the users actually understand the difference
So I will preface this by saying hopefully my comments are not taken the
wrong way and turn into a big fight but instead can lead to a productive
discussion about the next steps.
First, I'm certainly not opposed to anyone who wants to work on modernizing
and adding features to existing software.
Hi all,
I would like to discuss with you about the ActiveMQ 5.x roadmap.
Even if Artemis is there, the stack is different and we still have lot
of users on ActiveMQ, and, as a ActiveMQ 5.x fan and contributor, I
think it's worth to give a new "dimension" to ActiveMQ 5.x.
As all Apache projects,
10 matches
Mail list logo
