Here is a thread for some infrastructure implications of an OO podling. Things to note:
1. OO is very large. 2. OO is a good-old C++ giant. It's not 'build once, run anywhere'. It has to be built many times in many configurations to maintain regression testing. There is, in short, a detectable dollar cost in build machines to run all the builds needed to keep up with it. 3. OO has a well-establish development methodology which will be new and interesting at Apache. It is a very branch-intensive methodology, involving these CWS things. This, I think, is the root of the 'oh, no, svn' traffic. I've never seen extensive bi-directional merging work well in svn. If there was ever a job for a dvcs ... Perhaps, this can work by allowing the not-cooked-yet versions to be outboard in git, and coming up with a scheme to document provenance as they merge into svn. Perhaps not. Perhaps this really should be considered as a test case for the rw-git infrastructure that is under construction. But I don't think that it can be dismissed with a wave of the hand and a flat statement of 'svn works for everyone else at Apache.' --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
