Based on some conversations I want to get a thread going on the
following....
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 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
- C++ Client 0-10
- Ruby 0-10
- .NET 0-10 (see rabbit has done WCP layer, do we want pick anything up
from that as it is ASL, do we also want to support 0-8/9 from the same
client, updating our client...)
Other items:
- do we want to try have common events between brokers for mgmt?
- I expect that we will work to get the Java broker both 0-8/9 and 0-10
for M4
- Lot of DTX & JTA work has been done for Java how to review/ merge etc
this?
Let's refine the list on mail and then build a JIRA set for M3.
Also, do we expect we will need to do a M2.2 - if so what is it?
Carl.
