imported>Cewbot: Fixing broken anchor: Reminder of an inactive anchor: Helix Core

2025-06-10T21:09:14Z

Fixing broken anchor: Reminder of an inactive anchor: Helix Core

New page

{{Short description|none}}
This is a list of notable [[version control]] [[software system]]s.


==Common attributes==

*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 model|Client–server]], users access a master repository server via a [[Client (computing)|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 version control|Distributed]], repositories act as peers; typically each user has a local repository clone with complete version history in addition to their working files

==Active==

* [[AccuRev SCM|AccuRev]] [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]]
* [[IBM DevOps Code ClearCase|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
** [[OpenBSD#Open source and open documentation|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 configuration management|software change and configuration management]] system developed by [[Micro Focus International|Micro Focus]], formerly [[Serena Software]], that includes [[revision control]]
* [[Fossil (software)|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 <ref>{{Cite web |title=Git - A Short History of Git |url=https://git-scm.com/book/en/v2/Getting-Started-A-Short-History-of-Git |access-date=2023-10-29 |website=git-scm.com}}</ref>
* [[IC Manage|Global Design Platform]] (GDP) [proprietary, client-server] – design data management for IC design and [[Perforce]] infrastructure support
* [[PTC Integrity|Integrity]] [proprietary, client-server]
* [[Perforce Software#Helix Core|Helix Core]]{{Broken anchor|date=2025-06-10|bot=User:Cewbot/log/20201008/configuration|target_link=Perforce Software#Helix Core|reason= The anchor (Helix Core) [[Special:Diff/1294959325|has been deleted]].|diff_id=1294959325}} (formerly Perforce Helix) [proprietary, client-server] – for large scale development environments
* [[Mercurial (software)|Mercurial]] [open, distributed] – written in [[Python (programming language)|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]]<ref>{{Cite web |title=Plastic SCM - The Distributed Version Control for Big Projects |url=https://www.plasticscm.com/ |access-date=2023-10-29 |website=www.plasticscm.com}}</ref><ref>{{Cite web |last=Technologies |first=Unity |title=Scalable DevOps Services & Solutions {{!}} Unity |url=https://unity.com/products/unity-devops |access-date=2023-10-29 |website=unity.com |language=en}}</ref>
* [[PVCS]] [proprietary, client-server] – developed by Don Kinzer at [[Polytron (software company)|Polytron]], first released in 1985; now owned by [[Micro Focus]]
* [[Razor (configuration management)|Razor]] [proprietary, ?] – 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<ref name="wohler1">{{cite web |url=http://www.faqs.org/faqs/unix-faq/faq/part7/ |title=Unix – Frequently Asked Questions (7/7) |at=RCS vs SCCS: How do they compare for performance? |author=Bill Wohler |date=10 Oct 1992 |quote=[RCS ...] is much faster in retrieving the latest version}}</ref><ref name="mcvoy">{{cite web|url=http://mail.bitmover.com/pipermail/bitkeeper-users/2003-December/001137.html |title=BitKeeper: Why SCCS, rather than RCS? |author=Larry McVoy |date=11 Dec 2003 |quote=RCS is optimized for getting the most recent version on the trunk |url-status=dead |archive-url=https://web.archive.org/web/20120326025256/http://mail.bitmover.com/pipermail/bitkeeper-users/2003-December/001137.html |archive-date=March 26, 2012}}</ref> compared to SCCS and an improved user interface,<ref>{{cite web |url=http://www.faqs.org/faqs/unix-faq/faq/part7/ |title=Unix – Frequently Asked Questions (7/7) |at=RCS vs SCCS: How do the interfaces compare? |author=Bill Wohler |date=10 Oct 1992 |quote=[RCS ...] is more intuitive and consistent}}</ref> 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|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 (software)|branching]] and [[Merge (revision control)|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 (software)|Subversion]] (SVN) [open, client-server] – versioning control system inspired by CVS<ref>{{citation|url=http://svn.collab.net/repos/svn/trunk/CHANGES |title=SVN |chapter=Changes |publisher=Collab Net |url-status=dead |archive-url=https://web.archive.org/web/20081025054653/http://svn.collab.net/repos/svn/trunk/CHANGES |archive-date=October 25, 2008}}</ref>
* [[Surround SCM]] [proprietary, client-server] – version control tool by [[Seapine Software]]
* [[Telelogic Synergy|Synergy]] [proprietary, client-server] – MSSCCI compliant (Source Control Plug-in API) integrated change management and task-based configuration management system, proprietary of IBM
* [[IBM Rational Team Concert|Team Concert]] [proprietary, client-server] – Collaboration and application lifecycle management platform by [[IBM]] [[Rational Software]]
* [[Azure DevOps Server#TFVC|Team Foundation Version Control]] [proprietary, client-server] – version control system developed by [[Microsoft]] for Team Foundation Server, now [[Azure DevOps Server]]
* [[The Librarian (version control system)|The Librarian]] [proprietary, shared] – Around since 1969, source control for [[IBM mainframe]] computers; from [[Applied Data Research]], later acquired by [[Computer Associates]]
* [[Vault (revision control system)|Vault]] [proprietary, client-server] – version control tool by SourceGear; first installation can be used for free

== Obsolete ==

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

* [[Bazaar (software)|Bazaar]] [open, distributed] – written in [[Python (programming language)|Python]], originally by Martin Pool and sponsored by [[Canonical Ltd.|Canonical]]; decentralised: goals: fast and easy to use; can losslessly import Arch archives; replaced by friendly fork named [[Breezy (software)|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)
* [[IBM Configuration Management Version Control|Configuration Management Version Control]] (CMVC) [proprietary, client-server] – version control system, no longer available
* [[GNU arch]] [open, distributed] – A very early system; deprecated since 2009 in favor of Bazaar
* [[Distributed Concurrent Versions System|DCVS]] [open, distributed] – A decentralized spin on CVS, last released 2006 and since discontinued
* [[Monotone (software)|Monotone]] [open, distributed] – not updated since 2011
* [[QVCS|Quma Version Control System]] – [open] VCS, final release 2010, abandoned 2013
* [[Sun WorkShop TeamWare]] – Designed{{citation needed|date=February 2015}} by [[Larry McVoy]], creator of BitKeeper
* [[Vesta (Software configuration management)|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. Final release in 2005.

== See also ==
* [[Comparison of version-control software]]
* [[Comparison of source-code-hosting facilities]]

== References ==
{{Reflist}}

== External links ==

{{Version control software}}

[[Category:Version control systems|List of version control software]]
[[Category:Lists of software|Version control software]]

List of version-control software - Revision history

imported>Cewbot: Fixing broken anchor: Reminder of an inactive anchor: Helix Core