Distributed SCM: You Don#039;t Get It Until You Got It

Chris Adamson recently blogged, what are the advantages of distributed SCM, beyond the globe-spanning mega-projects? I#039;ve been hearing that question for a long time; it started whenever a new engineer joined a Sun project and had trouble getting their head around TeamWare. But it#039;s hard to answer that question except with, try it for a while and you#039;ll see. The reason that#039;s a hard question to answer is because a distributed SCM creeps up on you and changes the way you work, in a subtle way you don#039;t notice until you have to work on a single-repository SCM again. The reason is that branching is very easy on a distributed SCM and so you use it all the time; it#039;s so easy that you rarely notice you are branching. Anytime engineers want to work on something independently, whether it be in different cities across the globe, between co-workers, or just by themselves working on two projects at once, all you do is clone the repository you want to work with from some other copy, which becomes the parent of your new copy. Make any changes you like in this copy, then commit them when you like them as usual. Just like any other SCM, right? Wrong, as the commit only happens in your copy; you need to merge your copy with its parent to share it with the parent#039;s other child repositories. It sounds like more work, but it#039;s the opposite because it fits better with how most software engineers go about their job...

Date: September, 13 2008
Url: http://www.java.net/blog/2008/09/12/distributed-scm-you-dont-get-it-until-you-got-it

Others News