Tim noticed an issue with the while working on some changes to ActiveMQ:
https://issues.apache.org/jira/browse/QPID-6447
On 12 March 2015 at 12:52, Justin Ross justin.r...@gmail.com wrote:
Hi, everyone. Important defects were discovered soon after I published the
initial RC. Here is RC 2 from
Ah I think I misunderstood earlier then hehe.
I'd agree that if its long standing we should defer to a 0.32.1 point
release, unless something else comes up that requires a respin in
which case I would include it.
Robbie
On 12 March 2015 at 16:41, Timothy Bish tabish...@gmail.com wrote:
I
I wouldn't treat it as a blocker for the release, I'm pretty sure this
has been popping up in our CI for some time now.
On 03/12/2015 12:36 PM, Rob Godfrey wrote:
From looking at the code I don't think this is a new issue... I think
the same deadlock path would have been present in 0.30 and
From looking at the code I don't think this is a new issue... I think
the same deadlock path would have been present in 0.30 and prior
versions (the two codepaths appear to me to be unchanged since Jan
2014).
I have made what I think is a fix on trunk, but given it's not a new
issue I'm not sure
Hi, everyone. Important defects were discovered soon after I published the
initial RC. Here is RC 2 from revision 1666029.
Release artifacts: https://dist.apache.org/repos/dist/dev/qpid/0.32-rc2/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapacheqpid-1028
This
