On Tue, 2007-07-03 at 11:46 +0100, Gordon Sim wrote: > Arnaud Simon wrote: > > I think that the C++ repo is already in the process of being migrated to > > 0.10. > > As mentioned, at present c++ remains 0-9 WIP compliant. > > > Moreover 0.10 is already in an advanced state and starting to code > > it can only help spotting issues beforehand. > > This is a good point (and in implementing some of the 'previews' I have > noticed issues with the spec that can hopefully be dealt with by the WG > prior to publication). We don't have to break compliance on trunk from > whichever version to do this however.
Based on our previous failures at 0_8-0-9 migration I strongly suggest the following: 1. We do NOT break the build at any point. 2. We do NOT take a branch for the work Here's how I plan to do it for C++: 1. Clean separation of model from framing stack. This is pretty much already there. 2. Start building a *new* 0-10 framing stack *beside* the old stack. This may involve refactoring but *not breaking* the old stack. 3. Create new tests to verify the new stack, while continuing to test the old stack. 4. Only when the new stack passes equivalent set of tests to old, remove the old stack BUT. 5. Maybe we want to keep the old stack and have a multi-version broker? For C++ there's no value in keeping the 0-9 stack BUT there's tremendous value in not breaking it till we're finished with 0-10. One of the mistakes we made before was to start out by breaking the stack at the lowest layer, and then spend weeks in the dark because we couldn't test anything. With the model changes in 0-10 it'll be crucial that people can be working on the model layer AND the framing stack simultaneiously. Keeping the old stack will allow us to continue testing the model layer fed from the old stack till the new stack is ready.
