Navigation
  • Home
  • Recent
  • Most Active
  • Popular
  • Blog
  • Credits
  • RSS
    		•
      Interaction
  • Register
  • Statistics
    		•
      Help
  • Suggestions
  • Contact Us
  • How to Edit
  • Help
    		•



    [Edit]


    The following tables compare general and technical information for notable revision control and software configuration management (SCM) software. This article is not all-inclusive and may become out of date quickly.
        Comparison of revision control software
            General information
            Technical information
            Features
            User interfaces
            History and adoption
            See also

    top

    General information
    | class="wikitable" style="font-size: 85%; text-align: center; width: 100%;"
    |-
    ! Software
    ! Maintainer
    ! Development status
    ! Repository model
    ! License
    ! Platforms supported
    ! Cost
    |-
    ! | AccuRev *
    | AccuRev, Inc.*
    | actively developed
    | Client-server
    | Proprietary
    | Unix-like, Windows, Mac OS X
    | Contact AccuRev
    |-
    ! | Bazaar *
    | Canonical Ltd *
    | actively developed
    | Distributed
    | GPL
    | Unix-like, Windows, Mac OS X
    | Free
    |-
    ! | ClearCase *
    | IBM Rational *
    | actively developed
    | Client-server
    | Proprietary
    | Unix-like, Windows, Mac OS X
    | $4125 per seat plus tax (includes 12 months support)
    |-
    ! | Code Co-op *
    | Reliable Software
    | actively developed
    | Distributed
    | Proprietary
    | Windows
    | $159 per seat
    |-
    ! | CVS *
    | The CVS Team *
    | maintained but new features not added
    | Client-server
    | GPL
    | Unix-like, Windows, Mac OS X
    | Free
    |-
    ! | CVSNT *
    | March Hare Software * and community members.
    | maintained and new features under development
    | Client-server
    | GPL or proprietary
    | Unix-like, Windows, Mac OS X, OS/400
    | Free or commercial
    |-
    ! | darcs *
    | David Roundy
    | actively developed
    | Distributed
    | GPL
    | Unix-like, Windows, Mac OS X
    | Free
    |-
    ! | GNU arch *
    | Andy Tai
    | maintained but new features not added
    | Distributed
    | GPL
    | Unix-like, Windows, Mac OS X
    | Free
    |-
    ! | Git *
    | Junio C Hamano
    | actively developed
    | Distributed
    | GPL
    | POSIX
    | Free
    |-
    ! | Mercurial *
    | Matt Mackall
    | actively developed
    | Distributed
    | GPL
    | Unix-like, Windows, Mac OS X
    | Free
    |-
    ! | Monotone *
    | Nathaniel Smith, Graydon Hoare
    | actively developed
    | Distributed
    | GPL
    | Unix-like, Windows, Mac OS X
    | Free
    |-
    ! | Perforce *
    | Perforce Software Inc.
    | actively supported
    | Client-server
    | Proprietary
    | Unix-like, Windows, Mac OS X
    | Free for up to 2 users, and for OSS development; else $800 per seat, with volume discounts *
    |-
    ! | SourceHaven *
    | Veterisoft, Inc. *
    | actively supported
    | Client-server
    | Proprietary
    | Unix-like, Windows, Mac OS X
    | $295 per seat with volume discounts
    |-
    ! | StarTeam *
    | Borland *
    | actively developed
    | Client-server
    | Proprietary
    | Windows and Crossplattform via Java based client
    | Included with BDS2006 Enterprise and up, otherwise Contact Borland
    |-
    ! | Subversion *
    | CollabNet, Inc. *
    | actively developed
    | Client-server

    top

    Technical information
    | class="wikitable" style="font-size: 85%; text-align: center; width: 100%;"
    |-
    ! Software
    ! Programming language
    ! History model
    ! Revision IDs
    ! Repo. size
    ! Network protocols
    |-
    ! | AccuRev
    | C++
    | Changeset
    | Namespace
    | O(revisions)
    | custom
    |-
    ! | Bazaar
    | Python
    | Snapshot
    | Pseudorandom
    | O(patch)
    | HTTP, SFTP, FTP, email bundles

      History model describes the form in which changes are stored in the repository. For example, when a change is committed, a system could store a copy of the tree before and after the change (snapshot), or it might instead store a copy of the tree before the change and a changeset representing the changes.
      Revision IDs are used internally to identify specific versions of files in the repository. Systems may use pseudorandom identifiers, content hashes of revisions, or filenames with sequential version numbers (namespace).
      Repo. size describes how the repository grows as changes are committed. O(patch) means that it grows as the size of the patches between revisions, while O(revisions) means that it grows as the size of each revision checked in.
      Network protocols lists the protocols used for sychronization of changes.

    top

    Features
    | class="wikitable" style="font-size: 85%; text-align: center; width: 100%;"
    |-
    ! Software
    ! Atomic commits
    ! File renames
    ! Symbolic links
    ! Pre/post-event hooks
    ! Signed revisions
    ! Merge Points
    |-
    ! | AccuRev
    |
    |
    |
    |
    |
    |
    |-
    ! | Bazaar
    |
    |
    |
    |
    | *
      Atomic commits refers to a guarantee that all commits are merged fully, or not at all.
      File renames describes whether a system allows files to be renamed while retaining their version history.
      Symbolic links describes whether a system allows revision control of symbolic links as with regular files. Versioning symbolic links is considered by some people a feature and some people a security breach (eg a symbolic link to /etc/passwd). Symbolic links are only supported on select platforms, depending on the software.
      Pre/post event hooks indicates the capability to trigger commands before or after an action, such as a commit, takes place.
      Signed revisions refers to integrated digital signing of revisions, in a format such as OpenPGP.
      Merge Points refers to a way to identify which revisions were merged from what other revisions (usually from a branch to the Trunk, but could be vice-versa or even from an earlier revision on the trunk/branch to a later revision on the trunk/branch.

    top

    User interfaces

    top

    History and adoption


      Notable users is a list of well known projects using the software as their primary revision control system, excluding the software itself, followed by a link to a full list if available.
      History briefly describes the software's origins and development.

    top

    See also
     
    Search more:
     

       
    Source Privacy License Download Contact Us Atlas
    Scientus.org Dictionary (Yet Another Wiki) RC : 1.39
    This article is licensed under the GNU Free Documentation License [copyleft]. It uses material from the Wikipedia article "Comparison of revision control software". link