Michael Gall writes about revision control

Michael Gall over at wakeless.net has written a three-part series on revision control.

It's a good overall introduction to what revision control is, as well as the need for it and current weaknesses in the main revision control systems.

Michael makes the important point that integrating revision control into a developer's work flow should be a priority. The harder the revision control system is to use, the longer developers will take between committing changes. This increases the risk that multiple "logical" changes are grouped into one commit, making it so much harder to roll back a specific change if a defect is discovered. In my opinion, a defect should be handled by one and only one commit into the source tree.

I'll follow up with a look into the revision control I use every day in my work with IBM.

blog comments powered by Disqus