qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marnie McCormack <marnie.mccorm...@googlemail.com>
Subject Re: 0.6 Release Plans from now onwards
Date Thu, 17 Dec 2009 13:10:02 GMT
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.


On Tue, Dec 15, 2009 at 10:26 PM, Andrew Stitcher <astitcher@redhat.com>wrote:

> 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:dev-subscribe@qpid.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message