Apr06: Bill De Hora on the benefits of a DVCS like Git or [Mercur Ial]. I'm sick of branching hassles in Sub Version, so getting increasingly tempted....

Mar06'2008: [Luke Hoersten] on the shortcomings of [Mercur Ial].

[Ben Collins Sussman], a core Sub Version developer, wrote about the risks he perceived in DVCS back in 2005.

Apr22'2008: [David Glasser] considers the relative positions of Sub Version and DVCS, and its implications for a focus to future Sub Version development. My opinion? The Subversion project shouldn't spend any more time trying to make Subversion a better version control tool for non-huge open source projects. Subversion is already decent for that task, and other tools have greater potential than it. We need to focus on making Subversion the best tool for organizations whose users need to interact with repositories in complex ways.

[Ben Collins Sussman] replies we think that this will probably be the "final" centralized system that gets written in the open source world - it represents the end-of-the-line for this model of code collaboration. It will continue to be used for many years, but specifically it will gain huge mindshare in the corporate (Enter Prise) world, while (eventually) losing mindshare to distributed systems in the Open Source arena.

Lots of discussion on ReddIt. (Including people noting support for various DVCS systems in Trac Wiki.)

User Options Recent Changes Help Page