Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
List of version-control software
open-in-new
<h2 id="common-attributes">Common attributes</h2> <ul><li>Openness, whether the software is <i>open</i> source or <i>proprietary</i></li> <li>Repository model, how working and shared <a href="/facts/Source_code/o9J6Jv23">source code</a> is handled <ul><li>Shared, all developers use the same file system</li> <li><a href="/facts/Client%E2%80%93server_model/FSnf27C5">Client–server</a>, users access a master repository server via a <a href="/facts/Client_(computing)/u0wlVsWI">client</a>; 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</li> <li><a href="/facts/Distributed_version_control/PDAlqzRE">Distributed</a>, repositories act as peers; typically each user has a local repository clone with complete version history in addition to their working files</li></ul></li></ul> <h2 id="active">Active</h2> <ul><li><a href="/facts/AccuRev_SCM/eprDP9c4">AccuRev</a> [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 <a href="/facts/Micro_Focus/LuuMMtYQ">Micro Focus</a></li> <li><a href="/facts/Autodesk_Vault/WUg3JkYw">Autodesk Vault</a> [proprietary, client-server] – Version control tool specifically designed for <a href="/facts/Autodesk/6aydGFN5">Autodesk</a> applications managing the complex relationships between design files such as <a href="/facts/AutoCAD/c83IAlgP">AutoCAD</a> and <a href="/facts/Autodesk_Inventor/VsbUFHsP">Autodesk Inventor</a></li> <li><a href="/facts/CADES/5B6gyk6I">CADES</a> [proprietary, client-server] – Designer productivity and version control system by <a href="/facts/International_Computers_Limited/2ztan410">International Computers Limited</a></li> <li><a href="/facts/IBM_DevOps_Code_ClearCase/n2A6TAVS">ClearCase</a> [proprietary, client-server] – MSSCCI compliant (<a href="/facts/Source_Control_Plug-in_API/LsJlvcVq">Source Control Plug-in API</a>) configuration management system by <a href="/facts/IBM/QszA7nwd">IBM</a> <a href="/facts/Rational_Software/4CHGNRLY">Rational Software</a></li> <li><a href="/facts/Concurrent_Versions_System/PKnqSra2">Concurrent Versions System</a> (CVS) [open, client-server] – originally built on RCS, licensed under the <a href="/facts/GPL/S75KhLSX">GPL</a> <ul><li><a href="/facts/CVSNT/81CLfcAk">CVSNT</a> – cross-platform port of CVS that allows case insensitive file names among other changes</li> <li><a href="/facts/OpenBSD/xmPS9tek">OpenCVS</a> – unreleased CVS clone under a <a href="/facts/BSD_license/XLtmLp5x">BSD license</a>, emphasizing security and source code correctness</li></ul></li> <li><a href="/facts/Darcs/12vMLFET">Darcs</a> [open, distributed] – originally developed by David Roundy; track inter-patch dependencies and automatically rearrange and <i>cherry-pick</i> them using a <i>theory of patches</i></li> <li><a href="/facts/Dimensions_CM/vLqxU1GG">Dimensions CM</a> [proprietary, client-server] – <a href="/facts/Software_configuration_management/VReDo7g4">software change and configuration management</a> system developed by <a href="/facts/Micro_Focus_International/LuuMMtYQ">Micro Focus</a>, formerly <a href="/facts/Serena_Software/5sbtKyGN">Serena Software</a>, that includes <a href="/facts/Revision_control/pxCmFXqK">revision control</a></li> <li><a href="/facts/Fossil_(software)/FCS5tLY1">Fossil</a> [open, distributed] – written by <a href="/facts/D._Richard_Hipp/nznwWzbC">D. Richard Hipp</a> for <a href="/facts/SQLite/1PwYzIft">SQLite</a>; distributed revision control, wiki, bug-tracking, and forum (all-in-one solution) with console and web interfaces; single portable executable and single repository file</li> <li><a href="/facts/Git/U5Ty9QmQ">Git</a> [open, distributed] – designed by <a href="/facts/Linus_Torvalds/EdDKP534">Linus Torvalds</a> for <a href="/facts/Linux_kernel/dlkduHuA">Linux kernel</a> development; decentralized; goals: fast, flexible, and robust <a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a></li> <li><a href="/facts/IC_Manage/jpApau2I">Global Design Platform</a> (GDP) [proprietary, client-server] – design data management for IC design and <a href="/facts/Perforce/y9wI1f6T">Perforce</a> infrastructure support</li> <li><a href="/facts/PTC_Integrity/49hQ3gKp">Integrity</a> [proprietary, client-server]</li> <li><a href="/facts/Perforce_Software/y9wI1f6T">Helix Core</a> (formerly Perforce Helix) [proprietary, client-server] – for large scale development environments</li> <li><a href="/facts/Mercurial_(software)/lEkoYb6C">Mercurial</a> [open, distributed] – written in <a href="/facts/Python_(programming_language)/YbuGqofa">Python</a> as an open source replacement to <a href="/facts/BitKeeper/fahCmdSd">BitKeeper</a>; decentralized and aims to be fast, lightweight, portable, and easy to use</li> <li><a href="/facts/Panvalet/Q5YGPQ8R">Panvalet</a> [proprietary, shared] – Around since the 1970s, source and object control for IBM mainframe computers</li> <li><a href="/facts/Plastic_SCM/kv3X67EL">Plastic SCM</a> (rebranded as Unity Version Control) [open, proprietary] – by Codice Software, Inc and <a href="/facts/Unity_Technologies/XYuT93af">Unity Technologies</a><a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a><a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li> <li><a href="/facts/PVCS/nTV6BJtV">PVCS</a> [proprietary, client-server] – developed by Don Kinzer at <a href="/facts/Polytron_(software_company)/pExNRxM2">Polytron</a>, first released in 1985; now owned by <a href="/facts/Micro_Focus/LuuMMtYQ">Micro Focus</a></li> <li><a href="/facts/Razor_(configuration_management)/qFSENUb1">Razor</a> [proprietary, ?] – integrated suite from Visible Systems</li> <li><a href="/facts/Revision_Control_System/9rHoEV5Y">Revision Control System</a> (RCS) [open, shared] – stores the latest version and backward deltas for the fastest access to the trunk tip<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a><a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> compared to SCCS and an improved user interface,<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> at the cost of slow branch tip access and missing support for included/excluded deltas</li> <li><a href="/facts/Source_Code_Control_System/v85GIeBx">Source Code Control System</a> (SCCS) [open, shared] – part of <a href="/facts/Unix/0pNL2seI">UNIX</a>; based on <a href="/facts/Interleaved_deltas/v99uBTEF">interleaved deltas</a>, 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 <a href="/facts/Branching_(software)/1m0qK9tv">branching</a> and <a href="/facts/Merge_(revision_control)/776L9Du9">merging</a> with multiple "current" and identical versions</li> <li><a href="/facts/StarTeam/kmJJA7vc">StarTeam</a> [proprietary, client-server] – coordinates and manages software delivery process by <a href="/facts/Micro_Focus/LuuMMtYQ">Micro Focus</a>, formerly <a href="/facts/Borland/crI5pTzW">Borland</a>; centralized control of digital assets and activities</li> <li><a href="/facts/Subversion_(software)/b5j9wAbt">Subversion</a> (SVN) [open, client-server] – versioning control system inspired by CVS<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a></li> <li><a href="/facts/Surround_SCM/mR8k4MIB">Surround SCM</a> [proprietary, client-server] – version control tool by <a href="/facts/Seapine_Software/m4nk6G3o">Seapine Software</a></li> <li><a href="/facts/Telelogic_Synergy/ysWClyeT">Synergy</a> [proprietary, client-server] – MSSCCI compliant (Source Control Plug-in API) integrated change management and task-based configuration management system, proprietary of IBM</li> <li><a href="/facts/IBM_Rational_Team_Concert/4CHGNRLY">Team Concert</a> [proprietary, client-server] – Collaboration and application lifecycle management platform by <a href="/facts/IBM/QszA7nwd">IBM</a> <a href="/facts/Rational_Software/4CHGNRLY">Rational Software</a></li> <li><a href="/facts/Azure_DevOps_Server/DakBjeAh">Team Foundation Version Control</a> [proprietary, client-server] – version control system developed by <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a> for Team Foundation Server, now <a href="/facts/Azure_DevOps_Server/DakBjeAh">Azure DevOps Server</a></li> <li><a href="/facts/The_Librarian_(version_control_system)/AojrndyX">The Librarian</a> [proprietary, shared] – Around since 1969, source control for <a href="/facts/IBM_mainframe/0kPkgADx">IBM mainframe</a> computers; from <a href="/facts/Applied_Data_Research/qgq5HRDr">Applied Data Research</a>, later acquired by <a href="/facts/Computer_Associates/DErAtDJF">Computer Associates</a></li> <li><a href="/facts/Vault_(revision_control_system)/kMrUbyDy">Vault</a> [proprietary, client-server] – version control tool by SourceGear; first installation can be used for free</li></ul> <h2 id="obsolete">Obsolete</h2> <p>The following have been discontinued or not released in more than a decade. </p> <ul><li><a href="/facts/Bazaar_(software)/TQ3AEzcS">Bazaar</a> [open, distributed] – written in <a href="/facts/Python_(programming_language)/YbuGqofa">Python</a>, originally by Martin Pool and sponsored by <a href="/facts/Canonical_Ltd./76WPw1uW">Canonical</a>; decentralised: goals: fast and easy to use; can losslessly import Arch archives; replaced by friendly fork named <a href="/facts/Breezy_(software)/ntmlkhIg">Breezy</a></li> <li><a href="/facts/BitKeeper/fahCmdSd">BitKeeper</a> [open, distributed] – (discontinued) was used in <a href="/facts/Linux_kernel/dlkduHuA">Linux kernel</a> development (2002 – April 2005) until its license was revoked for breach of contract; open-sourced in 2016</li> <li><a href="/facts/Code_Co-op/GWenGgN9">Code Co-op</a> [open, proprietary] – (discontinued) peer-to-peer version control system (can use e-mail for synchronization)</li> <li><a href="/facts/IBM_Configuration_Management_Version_Control/CoRRQo2N">Configuration Management Version Control</a> (CMVC) [proprietary, client-server] – version control system, no longer available</li> <li><a href="/facts/GNU_arch/6qfhgXqX">GNU arch</a> [open, distributed] – A very early system; deprecated since 2009 in favor of Bazaar</li> <li><a href="/facts/Distributed_Concurrent_Versions_System/kGDoFnpI">DCVS</a> [open, distributed] – A decentralized spin on CVS, last released 2006 and since discontinued</li> <li><a href="/facts/Monotone_(software)/2Vk2E4hF">Monotone</a> [open, distributed] – not updated since 2011</li> <li><a href="/facts/QVCS/5YGQT2Ll">Quma Version Control System</a> – [open] VCS, final release 2010, abandoned 2013</li> <li><a href="/facts/Sun_WorkShop_TeamWare/4hwFE88P">Sun WorkShop TeamWare</a> – Designed by <a href="/facts/Larry_McVoy/fmjoAASt">Larry McVoy</a>, creator of BitKeeper</li> <li><a href="/facts/Vesta_(Software_configuration_management)/qmN91MBB">Vesta</a> [open, client-server] – (discontinued) build system with a versioning file system and support for distributed repositories</li> <li><a href="/facts/Visual_SourceSafe/PFXoBaae">Visual SourceSafe</a> (VSS) [proprietary, client-server] – version control tool by <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a>; oriented toward small teams. Final release in 2005.</li></ul> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Comparison_of_version-control_software/prfPW9sV">Comparison of version-control software</a></li> <li><a href="/facts/Comparison_of_source-code-hosting_facilities/pqq0GEjT">Comparison of source-code-hosting facilities</a></li></ul> <h2 id="external-links">External links</h2> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Git - A Short History of Git". git-scm.com. Retrieved 2023-10-29. <a href="https://git-scm.com/book/en/v2/Getting-Started-A-Short-History-of-Git" target="_blank">https://git-scm.com/book/en/v2/Getting-Started-A-Short-History-of-Git</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"Plastic SCM - The Distributed Version Control for Big Projects". www.plasticscm.com. Retrieved 2023-10-29. <a href="https://www.plasticscm.com/" target="_blank">https://www.plasticscm.com/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Technologies, Unity. "Scalable DevOps Services & Solutions | Unity". unity.com. Retrieved 2023-10-29. <a href="https://unity.com/products/unity-devops" target="_blank">https://unity.com/products/unity-devops</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>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 <a href="http://www.faqs.org/faqs/unix-faq/faq/part7/" target="_blank">http://www.faqs.org/faqs/unix-faq/faq/part7/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>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 <a href="https://web.archive.org/web/20120326025256/http://mail.bitmover.com/pipermail/bitkeeper-users/2003-December/001137.html" target="_blank">https://web.archive.org/web/20120326025256/http://mail.bitmover.com/pipermail/bitkeeper-users/2003-December/001137.html</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>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 <a href="http://www.faqs.org/faqs/unix-faq/faq/part7/" target="_blank">http://www.faqs.org/faqs/unix-faq/faq/part7/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Changes", SVN, Collab Net, archived from the original on October 25, 2008 <a href="https://web.archive.org/web/20081025054653/http://svn.collab.net/repos/svn/trunk/CHANGES" target="_blank">https://web.archive.org/web/20081025054653/http://svn.collab.net/repos/svn/trunk/CHANGES</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> </ol>