Re: 0.6 Release Plans from now onwards

2009-12-17 Thread Marnie McCormack
Hi Andrew, Thanks for the update. I've been trying to wade through code reviews/tidy ups to get the JIRAs in a better state. Anyone willing to pitch in on the Java reviews would be much appreciated. Marnie On Tue, Dec 15, 2009 at 10:26 PM, Andrew Stitcher astitc...@redhat.comwrote: As I

Re: 0.6 Release Plans from now onwards

2009-12-16 Thread Rajith Attapattu
On Tue, Dec 15, 2009 at 10:08 PM, Aidan Skinner aidan.skin...@gmail.com wrote: On Tue, Dec 15, 2009 at 11:46 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I came up against that a couple months ago. The reason seemed to be that the ConversationFactory is calling toString() on a message

0.6 Release Plans from now onwards

2009-12-15 Thread Andrew Stitcher
As I said in my beta release message I'd like to produce a release candidate at the end of this week. On the closing bugs front there are a couple of issues still (but nothing that looks deadly as far as I can tell): Essentially we have 2 blockers and 2 critical bugs. 2 Java bugs and 2 bugs for

Re: 0.6 Release Plans from now onwards

2009-12-15 Thread Aidan Skinner
On Tue, Dec 15, 2009 at 10:26 PM, Andrew Stitcher astitc...@redhat.com wrote: QPID-2273 (http://issues.apache.org/jira/browse/QPID-2273), QPID-1830 (http://issues.apache.org/jira/browse/QPID-1830) - Aidan can you give some status on these bugs? Are they going to be finished in the next couple

RE: 0.6 Release Plans from now onwards

2009-12-15 Thread Robbie Gemmell
It is actually possible to assign JIRA's to non-committers, I believe you just need to add the relevant JIRA account to the Contributors role for the project so that they show up as a possible assignee. Robbie -Original Message- From: Andrew Stitcher QPID-2260

RE: 0.6 Release Plans from now onwards

2009-12-15 Thread Robbie Gemmell
I came up against that a couple months ago. The reason seemed to be that the ConversationFactory is calling toString() on a message before its sent, and the toString() behaviour was changed from previously outputting the hash code to outputting actual content. (r756228 seems to be where you'd want

RE: 0.6 Release Plans from now onwards

2009-12-15 Thread Steve Huston
QPID-2260 (http://issues.apache.org/jira/browse/QPID-2260), QPID-2247 (http://issues.apache.org/jira/browse/QPID-2247) - These are more problematic as they don't have anyone assigned to them. It could be that Cliff is working on them, but as he isn't a commiter he can't be assigned the

Re: 0.6 Release Plans from now onwards

2009-12-15 Thread Aidan Skinner
On Tue, Dec 15, 2009 at 11:31 PM, Aidan Skinner aidan.skin...@gmail.com wrote: First sign of madness this, but never mind eh? On Tue, Dec 15, 2009 at 10:26 PM, Andrew Stitcher astitc...@redhat.com wrote: QPID-2273 (http://issues.apache.org/jira/browse/QPID-2273), QPID-1830

Re: 0.6 Release Plans from now onwards

2009-12-15 Thread Aidan Skinner
On Tue, Dec 15, 2009 at 11:46 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I came up against that a couple months ago. The reason seemed to be that the ConversationFactory is calling toString() on a message before its sent, and the toString() behaviour was changed from previously

Re: 0.6 Release Plans from now onwards

2009-12-15 Thread Rajith Attapattu
On Tue, Dec 15, 2009 at 10:08 PM, Aidan Skinner aidan.skin...@gmail.com wrote: On Tue, Dec 15, 2009 at 11:46 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I came up against that a couple months ago. The reason seemed to be that the ConversationFactory is calling toString() on a message

RE: 0.6 Release Plans from now onwards

2009-12-15 Thread Cliff Jansen (Interop Systems Inc)
in the various scenarios. Cliff -Original Message- From: Andrew Stitcher [mailto:astitc...@redhat.com] Sent: Tuesday, December 15, 2009 2:27 PM To: Qpid Dev List Subject: 0.6 Release Plans from now onwards As I said in my beta release message I'd like to produce a release candidate at the end