Article snapshot taken from Wikipedia with creative commons attribution-sharealike license.
Give it a read and then ask your questions in the chat.
We can research this topic together.
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
AccuRev – 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
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 – originally developed by David Roundy; track inter-patch dependencies and automatically rearrange and cherry-pick them using a theory of patches
Fossil – 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
Revision Control System (RCS) – stores the latest version and backward deltas for the fastest access to the trunk tip compared to SCCS and an improved user interface, 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 time and is thus more useful in environments that rely heavily on branching and merging with multiple "current" and identical versions
StarTeam – coordinates and manages software delivery process by Micro Focus, formerly Borland; centralized control of digital assets and activities
Subversion (SVN) – versioning control system inspired by CVS
Synergy – MSSCCI compliant (Source Control Plug-in API) integrated change management and task-based configuration management system, proprietary of IBM
Vault – 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 – 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 – (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 – (discontinued) peer-to-peer version control system (can use e-mail for synchronization)
Bill Wohler (10 Oct 1992). "Unix – Frequently Asked Questions (7/7)". RCS vs SCCS: How do they compare for performance?. is much faster in retrieving the latest version
Years, where available, indicate the date of first stable release. Systems with names in italics are no longer maintained or have planned end-of-life dates.
