Robert Greig wrote:
On 14/03/2008, Carl Trieloff <[EMAIL PROTECTED]> wrote:
It looks like M2.1 is landing nicely, so it might be time to start a
thread on M3 scope. M3 work
has begun as we all know but I think we need to block up what M3 will
looks like, JIRA it and do the
scope closing for it.
This all looks reasonable to me; my comment would be that we should
not make the scope too wide so that we can deliver a release that
gives real benefits in a reasonable time line, e.g. build complete by
June/July timeframe.
This is my view of what M3 looks like -- please add, rant, comment etc...
- Land the 'bigmergebranch' between M2.1 and truck
- Tests, tests and more tests...
- Java client M2.1(0-8/9) interop + AMQP 0-10
- Java broker merged (still talking 0-8/9?)
- Java broker (what else here??)
- C++ Broker 0-10 (TCP +IB)
- C++ Broker clustering module
Is clustering something that is likely to be ready for M3?
I'm aiming for fault-tolerant C++ broker and failover in at least C++, Java and
python clients in that time frame.
