On Wed, 2008-06-18 at 22:39 +0100, Robert Greig wrote: > 2008/6/18 Robert Godfrey <[EMAIL PROTECTED]>: > OK, so are we saying that we should release M3 as a "0-10 release", do > it soon, and only include those components that are close to > supporting 0-10 today (i.e. mostly done, just getting bug fixes etc). > This means C++ broker and client, java client and python client. M3 > would specifically exclude the ruby client, .NET client and java > broker? > > That sounds sensible to me - I completely agree that it would be great > to get a 0-10 release of AMQP out there. I do think that this will > require careful documentation to avoid confusing users (and potential > users).
I am +100 with that We should also start making a kind of planning. For example, I am volunteering for implementing .Net client 0.10 support. That should be ready for M3.1 (assuming we release M3 very soon). As we need a 8 weeks release process are we looking at this kind of agenda: -- week 26 Feature freeze + 6 weeks fix bugs -- week 32 fix Freeze + 2 weeks fix critical bugs -- week 34 Release M3 I believe we can shorten this release process (as a lot of testing has already been done on this code) by immediately starting the "fix Freeze" phase. We would then target a M3 release for week 28. We could then target M3.1 for early September. Note that I believe that the 6 weeks "fix bugs" could be shorten, especially if we want to release more often. Arnaud
