OK, given that this issue was recently introduced and is a regression
from 1.0.0, I think we should aim to get this fixed before doing a
1.1.0. It looks like the fix has already made it's way onto master. I
am going to cancel the vote and quickly turn around an RC4.
On 14/09/15 17:37, Clebert Suconic wrote:
On Mon, Sep 14, 2015 at 12:03 PM, Hiram Chirino <[email protected]>
wrote:
So if the MDB issue is a regression and there is a quick fix for it,
we might as well redo the 1.1 release to avoid giving users a bad
impression. If the issues was there in 1.0, then 1.1 would be no
worse than 1.0 and then this can wait for a 1.1.1 release.
Yes.. it is a regression on MDBs.. that's why I raised the -1.
The RA was broken at this commit here:
https://github.com/apache/activemq-artemis/commit/7a1199c4759a8b56ccb28e96f44b3ba760ca5316
And there is a fix proposed by Justin here:
https://github.com/apache/activemq-artemis/pull/169
