Ian Clatworthy, one of the primary developers of Bazaar, has posted a series of articles on version control in broad modern context.
His primary thesis is:
Beyond market acceptance, there are 6 main criteria I consider when evaluating collaboration tools:
- Reliability
- Adaptability
- Usability
- Extensibility
- Integration
- Administration (including Total Cost of Ownership)
Read the whole series at:
- “Version Control: The Future is Adaptive;
- “It Takes a Community to Raise Great Software”;
- “Wanted: Rock Solid Version Control”;
- “Version Control: Plug-ins vs Toolkits”;
- “Version Control: Design for Integration”;
Couple of memorable quotes:
Likewise, in the field of collaboration, I think there are 5 interesting numbers: 1, 2, 10, 100 and 1000. These numbers represent:
- an Individual
- a Partnership
- a Team
- a Company
- a Community
[...]
As a young software engineer back in the early 90s, 10s of thousands of people woke up to cold showers in Sydney one morning because of a corner-case bug in my code controlling the off peak hot water system. That sort of event tends to have a life long impact on how one designs software!
Recent posts on similar topics
- Subversion moves to ASF; Predicting bugs; updated SCM-Comparison. - November 6th, 2009
- RFC: let's make textual conflicts more personal - December 17th, 2008
- Dave Dribin: "Choosing a Distributed Version Control System" - February 10th, 2008
- Mark Shuttleworth on renaming and merging - October 7th, 2007
- Mark Shuttleworth on renaming and merging - October 7th, 2007