Justin-
Here are the notes from before the holidays:
https://issues.apache.org/jira/browse/ARTEMIS-898
It shouldn't break customer facing APIs. Just depends on your view of
versioning and if service-side change should result in a major rev bump
as well.
-Matt
On 2/9/17 11:08 AM, Justin Bertram wrote:
Can you elaborate on that, Matt? What exactly do you mean by "plugin support"?
What user-facing APIs would necessarily break?
Justin
----- Original Message -----
From: "Matt Pavlovich" <[email protected]>
To: [email protected]
Sent: Thursday, February 9, 2017 11:03:31 AM
Subject: Re: [DISCUSS] ActiveMQ Artemis 2.x stream
Martyn-
I think an important API breakage issue is plugin support.
-Matt
On 2/9/17 6:18 AM, Martyn Taylor wrote:
All,
As discussed in a previous thread [1] Artemis master has had a major bump
(due to major model refactor).
The great news is that the new model is more flexible and lends itself well
to 5.x features like Virtual Topics as well as being consistent across all
protocols. The not so good news is that this work required API breakages,
hence the major version bump.). This refactor work (mostly around the
addressing scheme [2]) is now completed.
The code base is now in a stable state, and as such, I'd like to start
thinking about doing a release off of master as an Apache Artemis 2.0.0 to
get the new changes into the hands of users.
I'd like to open discussion around this topic, does anyone have any
suggestions, or can think of anything that is needed before we go ahead
with a major release? This is the perfect time to do anything that could
break APIs, drop deprecated methods support, break data format etc...
Cheers
Martyn
[1]
http://activemq.2283324.n4.nabble.com/DISCUSS-Artemis-addressing-improvements-JMS-component-removal-and-potential-2-0-0-td4719262.html
[2] https://issues.apache.org/jira/browse/ARTEMIS-780
