Distributed version control: Difference between revisions

Revision as of 17:07, 1 January 2008

Revision as of 17:26, 1 January 2008

Line 1:

{{cleanup|date=November 2007}}

{{cleanup-laundry}}

{{merge|revision control#Distributed revision control|Talk:Distributed revision control#Merger proposal|date=January 2008}}

'''Distributed revision control''' (or '''Distributed Version Control (Systems) (DVCS)''', or '''Decentralized Version Control''') is a fairly recent innovation in [[Computer software|software]] [[revision control]]. It provides some significant advantages over the more traditional centralized approach to revision control, and it has some defining characteristics that separate it from centralized systems. However, the line between distributed and centralized systems is graying in some regards, especially since DVCSs can be used in a "centralized mode".

==Vs Centralised==

==Main Differences From Centralized==

Comparisons are often made between

==Main =Differences From Centralized===

* Each developer does work on her own local [[Software repository|repository]].

* Working model epitomizes [[The Cathedral and the Bazaar|bazaar]]-style development in that ''anyone'' can create their own [[Branching (software)|branch]].

Line 13 ⟶ 18:

* A separate set of "sync" operations are available for committing or receiving changes with remote repositories.

===Advantages vs Centralized===

* Allows users to work productively even when not connected to a network

* Makes most operations much faster since no network is involved

Line 20 ⟶ 25:

* Avoids relying on a single physical machine. A server disk crash is a non-event with Distributed revision control

===Disadvantages vs Centralized===

* Many teams have long used and grown accustomed to the centralized model, and are reluctant to change

* [[Source code]] is considered the "crown jewels" of a software group. Centralized VCSs have been around much longer and thus perceived to be more stable