The completed interop test client/coordinator for Java will be committed soon. Alan, I see you have already created a JIRA for the C++ client, we should create them for the other languages too. Split up QPID-242 and link it to one for each language instead.
I'm thinking that I will put the interop tests on the M2 branch, as it'd be good to be able to demonstrate that it really does work. Will merge accross to trunk and adapt from there as it evolves. Unless someone else steps in to volunteer? I will keep an eye on the .Net client as a low priority background task. Maybe you could provide some sort of running commentary as you change the c++/python clients so that the process can be mirrored for the others? Rupert On 3/19/07, Alan Conway <[EMAIL PROTECTED]> wrote:
A general point raised by this thread: how do we manage changes that break interop across all the projects. A fine time to raise it since I'm about to do exactly that :) I suggest the person who makes such a change should do one of the following, in decreasing order of preference: 1) Find an interoperable way to solve the problem :) 2) Apply the fix across all the projects in the same commit. 3) Find volunteers to make the fixes in other projects & co-ordinate commits. I'm taking the high road (1) for python, and will be taking the low road (3) on the rest of the codebase. Do we have volunteers to move the other projects to 0-9? I know we do for Java, what about .NET and ruby? Any ideas about timeframe? I'd like to say that we should never break interop for any extended period but I think it's inevitable for the 0-9 branch. I'm maintaining python as a bilingual link between C++ and Java. I confess I really didn't think about .Net and ruby until I started spouting off above. Cheers, Alan.
