In the local-only approach, all developers must use the same computer system. These software often manage single files individually and are largely replaced or embedded within newer software.
Open source
Revision Control System (RCS) – stores the latest version and backward deltas for fastest access to the trunk tip[1][2] compared to SCCS and an improved user interface,[3] 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 speed and is thus more useful in environments that rely heavily on branching and merging with multiple "current" and identical versions.
Client-server model
In the client-server model, developers use a shared single repository.
CVSNT – cross-platform port of CVS that allows case insensitive file names among other changes
OpenCVS – CVS clone under the BSD license, with emphasis put on security and source code correctness
Subversion (svn) – versioning control system inspired by CVS[4]
Vesta – build system with a versioning file system and support for distributed repositories
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
CA Software Change Manager (originally Harvest/CCC) – 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.
PVCS – originally Polytron Version Control System, developed by Don Kinzer at Polytron, first released in 1985. Now owned by Serena.
Quma Version Control System
SourceAnywhere – version control tool by Dynamsoft.
StarTeam – coordinates and manages software delivery process by Microfocus, formerly 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 Application Lifecycle Management (previously 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
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.
Open source
Aegis – written by Peter Miller, mature software, filesystem-oriented, limited network support. It has support for distributed revision control. It has built-in support for a disciplined process, including peer review and regression testing.
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 and sponsored by Canonical; 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"
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; decentralized, and aims to be fast, flexible, and robust
Mercurial – written in Python as an Open Source replacement to BitKeeper; decentralized 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
Veracity - Is another distributed version control system which includes bug tracking and Agile software development tools integrated with the version control features.
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.
Tags: List of revision control software, Teknik Informatika, 464, Daftar/Tabel revision control software This is a list of notable software for revision control, Contents Local data model 1.1 Open source 2 Client server model 2.1 Open source 2.2 Proprietary 3 Distributed model 3.1 Open source 3.2 Proprietary 4 Notes 5 See also 6 External links 6.1 Other comparisons 6.2 Further reading Local data model In the local only approach all developers must use the sa, List of revision control software, Bahasa Indonesia, Contoh Instruksi, Tutorial, Referensi, Buku, Petunjuk pasar, pts-ptn.net