Carl Trieloff wrote:
We need to pick a close down date for M5, and then it would be good for
everyone to list the key things they want to do for it. I have started a
list here:
http://cwiki.apache.org/confluence/display/qpid/looking+to+pitch+in
Please add / edit as needed. I am thinking close down for M5 in March.
On the c++ side I would personally like to see a relatively light list
of features (selectors, priorities) with more focus on consolidation
(e.g. ensuring that federation, clustering, ssl, sasl security layers,
rdma etc all work well in combination) and perhaps some work on performance.
I'd also like to make sure we have plenty of time so that we can ensure
the out-of-box experience across all components (individually and as a
collective) is as good as we can make it.
One specific question I'd like to raise is getting interop between all
components. I think that is a very important goal. Can we manage it for
the next release? I think the best way to do that would be 0-10 support
for the java broker.
