Categories
  Encyclosphere.org ENCYCLOREADER
  supported by EncyclosphereKSF

List of version-control software

From Wikipedia - Reading time: 7 min

This is a list of notable version control software systems.

Common attributes

[edit]
  • Openness, whether the software is open source or proprietary
  • Repository model, how working and shared source code is handled
    • Shared, all developers use the same file system
    • Client–server, users access a master repository server via a client; typically, a client machine holds only a working copy of a project tree; changes in one working copy are committed to the master repository before becoming available to other users
    • Distributed, repositories act as peers; typically each user has a local repository clone with complete version history in addition to their working files

Active

[edit]
  • AccuRev [proprietary, client-server] [proprietary, client-server] – source configuration management tool with integrated issue tracking based on "Streams" that manages parallel and global development; replication server is also available; now owned by Micro Focus
  • Autodesk Vault [proprietary, client-server] – Version control tool specifically designed for Autodesk applications managing the complex relationships between design files such as AutoCAD and Autodesk Inventor
  • CADES [proprietary, client-server] – Designer productivity and version control system by International Computers Limited
  • ClearCase [proprietary, client-server] – MSSCCI compliant (Source Control Plug-in API) configuration management system by IBM Rational Software
  • Concurrent Versions System (CVS) [open, client-server] – originally built on RCS, licensed under the GPL
    • CVSNT – cross-platform port of CVS that allows case insensitive file names among other changes
    • OpenCVS – unreleased CVS clone under a BSD license, emphasizing security and source code correctness
  • Darcs [open, distributed] – originally developed by David Roundy; track inter-patch dependencies and automatically rearrange and cherry-pick them using a theory of patches
  • Dimensions CM [proprietary, client-server] – software change and configuration management system developed by Micro Focus, formerly Serena Software, that includes revision control
  • Fossil [open, distributed] – written by D. Richard Hipp for SQLite; distributed revision control, wiki, bug-tracking, and forum (all-in-one solution) with console and web interfaces; single portable executable and single repository file
  • Git [open, distributed] – designed by Linus Torvalds for Linux kernel development; decentralized; goals: fast, flexible, and robust [1]
  • Global Design Platform (GDP) – [proprietary, client-server] design data management for IC design and Perforce infrastructure support
  • Integrity
  • Helix Core (formerly Perforce Helix) [proprietary, client-server] – for large scale development environments
  • Mercurial [open, distributed] – written in Python as an open source replacement to BitKeeper; decentralized and aims to be fast, lightweight, portable, and easy to use
  • Panvalet [proprietary, shared] – Around since the 1970s, source and object control for IBM mainframe computers
  • Plastic SCM (rebranded as Unity Version Control) [open, proprietary] – by Codice Software, Inc and Unity Technologies[2][3]
  • PVCS [proprietary, client-server] – developed by Don Kinzer at Polytron, first released in 1985; now owned by Micro Focus
  • Razor, integrated suite from Visible Systems
  • Revision Control System (RCS) [open, shared] – stores the latest version and backward deltas for the fastest access to the trunk tip[4][5] compared to SCCS and an improved user interface,[6] at the cost of slow branch tip access and missing support for included/excluded deltas
  • Source Code Control System (SCCS) [open, shared] – part of UNIX; based on interleaved deltas, can construct versions as arbitrary sets of revisions; extracting an arbitrary version takes essentially the same time and is thus more useful in environments that rely heavily on branching and merging with multiple "current" and identical versions
  • StarTeam [proprietary, client-server] – coordinates and manages software delivery process by Micro Focus, formerly Borland; centralized control of digital assets and activities
  • Subversion (SVN) [open, client-server] – versioning control system inspired by CVS[7]
  • Surround SCM [proprietary, client-server] – version control tool by Seapine Software
  • Synergy [proprietary, client-server] – MSSCCI compliant (Source Control Plug-in API) integrated change management and task-based configuration management system, proprietary of IBM
  • Team Concert [proprietary, client-server] – Collaboration and application lifecycle management platform by IBM Rational Software
  • Team Foundation Version Control [proprietary, client-server] – version control system developed by Microsoft for Team Foundation Server, now Azure DevOps Server
  • The Librarian [proprietary, shared] – Around since 1969, source control for IBM mainframe computers; from Applied Data Research, later acquired by Computer Associates
  • Vault [proprietary, client-server] – version control tool by SourceGear; first installation can be used for free

Obsolete

[edit]

The following have been discontinued or not released in more than a decade.

  • Bazaar – [open, distributed] written in Python, originally by Martin Pool and sponsored by Canonical; decentralised: goals: fast and easy to use; can losslessly import Arch archives; replaced by friendly fork named Breezy
  • BitKeeper [open, distributed] – (discontinued) was used in Linux kernel development (2002 – April 2005) until its license was revoked for breach of contract; open-sourced in 2016
  • Code Co-op [open, proprietary] – (discontinued) peer-to-peer version control system (can use e-mail for synchronization)
  • Configuration Management Version Control (CMVC)[proprietary, client-server] – version control system, no longer available
  • GNU arch - A very early [open, distributed]; deprecated since 2009 in favor of Bazaar
  • DCVS – A decentralized spin on CVS, last released 2006 and since discontinued
  • Monotone – [open, distributed], not updated since 2011
  • Quma Version Control System – [open] VCS, final release 2010, abandoned 2013
  • Sun WorkShop TeamWare – Designed[citation needed] by Larry McVoy, creator of BitKeeper
  • Vesta [open, client-server] – (discontinued) build system with a versioning file system and support for distributed repositories
  • Visual SourceSafe (VSS) [proprietary, client-server] – version control tool by Microsoft; oriented toward small teams

See also

[edit]

References

[edit]
  1. ^ "Git - A Short History of Git". git-scm.com. Retrieved 2023-10-29.
  2. ^ "Plastic SCM - The Distributed Version Control for Big Projects". www.plasticscm.com. Retrieved 2023-10-29.
  3. ^ Technologies, Unity. "Scalable DevOps Services & Solutions | Unity". unity.com. Retrieved 2023-10-29.
  4. ^ Bill Wohler (10 Oct 1992). "Unix – Frequently Asked Questions (7/7)". RCS vs SCCS: How do they compare for performance?. [RCS ...] is much faster in retrieving the latest version
  5. ^ Larry McVoy (11 Dec 2003). "BitKeeper: Why SCCS, rather than RCS?". Archived from the original on March 26, 2012. RCS is optimized for getting the most recent version on the trunk
  6. ^ Bill Wohler (10 Oct 1992). "Unix – Frequently Asked Questions (7/7)". RCS vs SCCS: How do the interfaces compare?. [RCS ...] is more intuitive and consistent
  7. ^ "Changes", SVN, Collab Net, archived from the original on October 25, 2008
[edit]
Licensed under CC BY-SA 3.0 | Source: https://en.wikipedia.org/wiki/List_of_version-control_software
12 views |
↧ Download as ZWI file
Encyclosphere.org EncycloReader is supported by the EncyclosphereKSF