> Cliff can you comment on these bugs? Are they truly as important as > blocker/critical? If so unless there are patches attached to the jiras > very soon I think we'll have to omit the specific WCF source code from > this release [...]
Agreed. These were marked as such because they would make a significant difference to early adopters and were thought to be doable *without* holding up the release. Right now, I feel comfortable about resolving QPID-2247 (and even QPID-2128) by tomorrow and QPID-2260 certainly by Thursday. The latter is very easy conceptually and boils down to testing in the various scenarios. Cliff -----Original Message----- From: Andrew Stitcher [mailto:[email protected]] 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 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 the WCF code. 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 of days? Is there much risk in the fixes? 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 bugs in Jira. Cliff can you comment on these bugs? Are they truly as important as blocker/critical? If so unless there are patches attached to the jiras very soon I think we'll have to omit the specific WCF source code from this release (of course it will still be in the big source tarball). To be honest I'm really sure it's quite mature enough in any case. Assuming that we can clear these issues up (one way or another) in the next couple of days - I plan to release rc1 on Thursday/Friday this week. I will create a (preemptive) subversion tag at that point. From that point I'd like to *freeze* checkins to the tree for 2 weeks taking us effectively to the new year. If we haven't actually voted to release by then I suggest we move the branch tag to whatever the most recent qpid checkin is and do all subsequent release work on a branch, and unfreeze the trunk. This way we should have the minimum frozen time and still be able to progress. Regards Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
