The plan is to get M2 to a releasable point, and for it to be the final, stable, version of Qpid that uses the 0-8 version of the protocol. Fixes we add to M2 will be merged down on to trunk.
The multi-version stuff being checked into trunk was (unfortunately) my error... The only one of those changes that I haven't backed out is changes to the code generator to allow it to use Velocity templates as well as the original template format. trunk for the C++ now has 0-9 support I believe... I'm not sure whether we'll bother with 0-9 support on the Java side, or jump straight to 0-10. AMQP 0-10 (which isn't finalised yet) is going to be a much bigger jump. All refactoring type work should be aimed at trunk also, I think... Thoughts? Rob On 19/04/07, Martin Ritchie <[EMAIL PROTECTED]> wrote:
Trunk should be where we do all our new development. I'm using M2 for bug fixing a few issues though some of them "fixes" seem to be more like new features. I hope to be merging my changes to trunk next week. So we can all work forward on trunk. On 19/04/07, Tomas Restrepo <[EMAIL PROTECTED]> wrote: > > OK, bit the bullet and checked out a copy of the M2 branch as well. > > > (P.S. It would seem the multiple protocol versions support in the java > > client causes it to freak out when it gets a connection.start method > > with an > > unsupported protocol version). > > Scratch that. The M2 branch freaks out as well on an unexpected protocol > version. > > > Tomas Restrepo > http://www.winterdom.com/weblog/ > > > > > -- Martin Ritchie
