Source Control

At the project I'm working on, they've just decided how they want Source Control Management to be done. Ok, Subversion - check, auto-build - check.

The interesting part is more to do with the number of streams and the intent of the different streams. We have one for just design, in which the modeling files are worked on, although stub java implementation classes need to be added/updated according to model changes, then a separate stream for development, which relies on a copy of the model files and allows the developer to code the actual implementation.

Problems arise though, if someone else changes the design stream to (naturally) rework an interface or two, since although they may update the impl stub in the design stream (to ensure it all compiles ok) they won't go fix what they've broken consequently in the dev stream. Of course then everyone else sees that the dev stream is broken, most likely more than one developer decides to fix it, then you've got more fun and games at commit time...

At this point in the narrative, I should probably be getting a bit annoyed. Just shows how long I've been on the project that I'm not too fussed, although I will probably point out to the customer how things could be done better, once they're beginning to get a flavour of the issues at hand.