List of revision control software
From Wikipedia, the free encyclopedia
This is a list of notable software for revision control.
Contents |
[edit] Local only
In the local-only approach, all developers must use the same computer system.
[edit] Free
- Revision Control System (RCS) — features separate backward deltas for faster 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
[edit] Distributed model
In the distributed approach, each developer works directly with his or her own local repository, and changes are shared between repositories as a separate step.
[edit] Open source
- Aegis — written by Peter Miller, mature software, filesystem-oriented, limited network support
- ArX — written by Walter Landry, started as a fork of GNU arch, but has been completely rewritten
- Bazaar — written in Python, originally by Martin Pool; decentralised, and aims to be fast and easy to use; can losslessly import Arch archives
- Codeville — written in Python originally by Ross Cohen; uses an innovative merging algorithm
- Darcs — written in Haskell and originally developed by David Roundy; can keep track of inter-patch dependencies and automatically rearrange and "cherry-pick" them using a "theory of patches"
- DCVS — decentralized and CVS-based
- Fossil — distributed revision control, wiki, and bug-tracking
- Git — written in a collection of Perl, C, and various shell scripts, designed by Linus Torvalds based on the needs of the Linux kernel project; decentralised, and aims to be fast, flexible, and robust
- GNU arch
- LibreSource — configuration management
- Mercurial — written in Python as an Open Source replacement to BitKeeper; decentralised and aims to be fast, lightweight, portable, and easy to use
- Monotone — developed by the Monotone Team; decentralized in a peer-to-peer way
- SVK — written in Perl by Kao Chia-liang; built on top of Subversion to allow distributed commits
[edit] Proprietary
- BitKeeper — was used in Linux kernel development (2002 – April 2005)
- Code Co-op — peer-to-peer version control system (can use e-mail for synchronization)
- Plastic SCM - a revision control tool that can function in both client/server and distributed modes
- Sun WorkShop TeamWare — designed by Larry McVoy, creator of BitKeeper
[edit] Client-server model
In the client-server model, developers use a shared single repository.
[edit] Open source
- Concurrent Versions System (CVS) — originally built on RCS
- CVSNT - cross-platform port of CVS that allows case insensitive file names among other changes
- OpenCVS - compatible with CVS, with emphasis put on security and source code correctness
- Subversion (svn) — initially released in 2000[1].
- Vesta — build system with a versioning file system and support for distributed repositories
[edit] Proprietary
- AccuRev — source configuration management tool with integrated issue tracking based on "Streams" that efficiently manages parallel and global development; replication server is also available
- AllFusion Harvest Change Manager — change and configuration management tool by Computer Associates
- Autodesk Vault - Version control tool specifically designed for Autodesk applications managing the complex relationships between design files such as AutoCAD and Autodesk Inventor.
- ClearCase — SCC compliant configuration management system by IBM Rational Software
- IBM Configuration Management Version Control (CMVC) — version control system, no longer available.
- codeBeamer - Collaboration and application lifecycle management platform
- Perforce — Free for use in open source projects.
- Polytron Version Control System (PVCS) — originally developed by Don Kinzer at Polytron, first released in 1985
- Quma Version Control System
- StarTeam — coordinates and manages software delivery process by Borland; centralized control of digital assets and activities
- Telelogic Synergy - SCC compliant 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)
- Visual SourceSafe — version control tool by Microsoft; oriented toward small teams
- Visual Studio Team System — process-based client-server suite of tools by Microsoft for larger development organizations, incorporating work item tracking, reporting, build automation, unit and web testing, and integration with Microsoft Office
[edit] Notes
[edit] See also
- Comparison of revision control software
- Revision control
- Comparison of free software hosting facilities
[edit] External links
[edit] Other comparisons
- Comments on Open Source Software / Free Software (OSS/FS) Software Configuration Management (SCM) Systems
- Quick Reference Guide to Free Software Revision Control Systems
- A comparison of some of both proprietary and free of these revision control systems
- Version-Control Systems for Linux
- SCM Price / Feature Comparison ( from the creators of Code Co-op )
[edit] Further reading
- Bram Cohen's blog entry on version control politics surrounding the Linux kernel (founder and contributor of Codeville), as of 2005-04-23
- Dispelling Subversion FUD by Ben Collins-Sussman (Subversion developer), as of 2004-12-21
- LWN article: "The Monotone version control system", as of 2005-04-13
- Configuration Management Tools at the Open Directory Project
- IETF Delta-V Working Group -- Extending the Web with versioning and configuration management... (WebDAV)
|
|||||||||||||||||||||||||||||||
