List of revision control software

From Wikipedia, the free encyclopedia
Jump to: navigation, search

This is a list of notable software for revision control.

Local data model[edit]

In the local-only approach, all developers must use the same file system.

Open source[edit]

  • Revision Control System (RCS) – stores the latest version and backward deltas for fastest access to the trunk tip[1][2] compared to SCCS and an improved user interface,[3] at the cost of slow branch tip access and missing support for included/excluded deltas.
  • Source Code Control System (SCCS) – part of UNIX; based on interleaved deltas, can construct versions as arbitrary sets of revisions. Extracting an arbitrary version takes essentially the same speed and is thus more useful in environments that rely heavily on branching and merging with multiple "current" and identical versions.

Client-server model[edit]

In the client-server model, developers use a shared single repository.

Open source[edit]

  • Concurrent Versions System (CVS) – originally built on RCS, licensed under the GPL.
    • CVSNT – cross-platform port of CVS that allows case insensitive file names among other changes
    • OpenCVS – CVS clone under the BSD license, with emphasis put on security and source code correctness
  • Subversion (SVN) – versioning control system inspired by CVS[4]
  • Vesta – build system with a versioning file system and support for distributed repositories

Proprietary[edit]

Distributed model[edit]

In the distributed approach, each developer works directly with his or her own local repository, and changes are shared between repositories as a separate step.

Open source[edit]

  • Aegis – written by Peter Miller, mature software, filesystem-oriented, limited network support. It has support for distributed revision control. It has built-in support for a disciplined process, including peer review and regression testing.
  • ArX – written by Walter Landry, started as a fork of GNU arch, but has been completely rewritten
  • Bazaar – written in Python, originally by Martin Pool and sponsored by Canonical; decentralised, and aims to be fast and easy to use; can losslessly import Arch archives
  • Codeville – written in Python originally by Ross Cohen; uses an innovative merging algorithm
  • Darcs – written in Haskell and originally developed by David Roundy; can keep track of inter-patch dependencies and automatically rearrange and "cherry-pick" them using a "theory of patches"
  • DCVS – decentralized and CVS-based
  • Fossil – written by D. Richard Hipp for SQLite; distributed revision control, wiki, and bug-tracking
  • Git – written in a collection of Perl, C, and various shell scripts, designed by Linus Torvalds based on the needs of the Linux kernel project; decentralized, and aims to be fast, flexible, and robust
  • GNU arch
  • LibreSource – configuration management
  • Mercurial – written in Python as an Open Source replacement to BitKeeper; decentralized and aims to be fast, lightweight, portable, and easy to use
  • Monotone – developed by the Monotone Team; decentralized in a peer-to-peer way
  • SVK – written in Perl by Kao Chia-liang; built on top of Subversion to allow distributed commits
  • Veracity - Is another distributed version control system which includes bug tracking and Agile software development tools integrated with the version control features.

Proprietary[edit]

Notes[edit]

  1. ^ Bill Wohler (10 Oct 1992). "RCS vs SCCS: How do they compare for performance?". Unix — Frequently Asked Questions (7/7). "[RCS ...] is much faster in retrieving the latest version" 
  2. ^ Larry McVoy (11 Dec 2003). "BitKeeper: Why SCCS, rather than RCS?". "RCS is optimized for getting the most recent version on the trunk" 
  3. ^ Bill Wohler (10 Oct 1992). "RCS vs SCCS: How do the interfaces compare?". Unix — Frequently Asked Questions (7/7). "[RCS ...] is more intuitive and consistent" 
  4. ^ "Changes", SVN, Collab Net [dead link]

See also[edit]

External links[edit]