Dave Dribin wrote a couple of posts on choosing between the usual suspects: Mercurial, Bazaar and Git. Well-written, recommended.
Read at: Choosing a Distributed Version Control System; follow-up: Why I Chose Mercurial.
Dave Dribin wrote a couple of posts on choosing between the usual suspects: Mercurial, Bazaar and Git. Well-written, recommended.
Read at: Choosing a Distributed Version Control System; follow-up: Why I Chose Mercurial.
Mark Shuttleworth (of Thawte, Ubuntu, and Canonical fames) wrote four posts on rename tracking feature in version control systems, and its impact on merging as a social process.
Read at his blog:
Those posts caught a lot of attention back in June, but frankly it seems to me the issue is somewhat overrated (but nevertheless a recommended reading). Mark’s Canonical Ltd. supports the development of Bazaar. Bazaar has the discussed feature of merging with renames tracking. Git does not have it, but it has another argument in this discussion: huge merging traffic — Linux kernel development is all about merging, and the codebase is huge. So, I guess this feature is not that crucial: Linus is well-known by his uncompromising approach to tools.
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:
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!