History of version-control systems (Wiki textbook Team4): Difference between revisions
No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
=Bazaar= | =Bazaar= | ||
Bazaar is one of the most famous distributed style tree versioning tool. Distributed structure is superior to central style version control systems in [ http://wiki.bazaar.canonical.com/BzrWhy many terms]. | Bazaar is one of the most famous distributed style tree versioning tool. Distributed structure is superior to central style version control systems in [http://wiki.bazaar.canonical.com/BzrWhy many terms]. | ||
= Summary = | = Summary = | ||
Using VCS has many benefits. For example: if a team conducts the project, there will be harmony among the team members, and no one will write over other people’s code. Moreover, every change (version) will be stored in VCS repository. This will enable team members to see the differences between versions of the same file, and they will know the time of the changes as well as the responsible team member. Furthermore, Development can be spit into different branches, each branch, lets say keeping track of the fixes associated with a software release. Then file versions can be obtained with a branch and can be applied to the same fix to multiple branches. Another benefit is that, VCS repository can be useful to understand how good the project was: How many lines changed from the previous version? Which are the most and least productive days of the week? Which team member made the most contribution? [7] | |||
== References == | == References == | ||
| Line 63: | Line 63: | ||
[http://en.wikipedia.org/wiki/Revision_Control_System] | [http://en.wikipedia.org/wiki/Revision_Control_System] | ||
: Version Control Systems,” by Diomidis Spinellis (IEEE Software, vol. 22, no. 5, 2005, pp. 108–109) | |||
Revision as of 17:39, 6 September 2010
"A source code system is a giant UNDO key-a project-wide time machine"
-Andy Hunt and Dave Thomas
Introduction
Dozens of version control systems are available in the market. Most of them are open source and free. First version control system was released in the early 1970s and new tools are released even today. Briefly, VCSs can be categorized into four [1]:
- File versioning tools, examples: SCCS, RCS
- Tree versioning Tools-central style, example: CVS
- Tree versioning tools-central style, example: Subversion
- Tree versioning tool-distributed style, example Bazaar
Source Code Control System
The very first version control system[5] is the Source Code Control System, which was originally written by Marc J. Rochkind in 1972 at Bell Labs, NJ. It is designed to help programming projects control changes to source code. SCCS provides facilities for storing, updating and retrieving all versions of modules by version number, and it records: who made software change, when and where it was made as well as the reason of the change. The first two implementations of SCCS were: one for IBM 370 under OS and other one for PDP 11under UNIX. [2][3]
Source Code control System can be categorized under file versioning tools. It only versions individual files. SCCS was an effective method for small projects. One Source file results in one SCCS history file. It is easy to understand format of the history files that allows manual intervention. Also, checksums and forward deltas grant file integrity and immediate detection of corruption. It was the major form of source code control especially on UNIX platforms until the release of Revision Control Systems.
Revision Control System
Revision Control System[7] is the successor to SCCS and written by Walter F. Tichy (now a faculty of University Karlsruhe, Germany) in 1982 at Purdue University. Just like SCCS, RVS is a file versioning tool. The fundamental storage unit is a revision group. Also it supports branches within a file. Unlike SCCS it supports merges. RCS storage on the mainline uses reserve deltas: The latest revision is stored intact but earlier revisions are stored as deltas from the latest. On branches, revisions are stored as forward deltas. Thus checking out branches is slow. For Example:Main line of code has 100 revisions. Assume that there is branch at revision 10. This branch has 80 revisions. To check out the branch tip, RCS must do the followings:
- Retrieve mainline revision 100
- Retrieve and apply reverse deltas from 99 down to 10
- Retrieve and apply 80 forward deltas on the branch
Additionally, in the early 80s, when RCS was released, there were also competitors such as: IBM CLEAR/CASTER, AT&T SCCS, and CMU Software Development control system.
Concurrent Version System
SVN
Bazaar
Bazaar is one of the most famous distributed style tree versioning tool. Distributed structure is superior to central style version control systems in many terms.
Summary
Using VCS has many benefits. For example: if a team conducts the project, there will be harmony among the team members, and no one will write over other people’s code. Moreover, every change (version) will be stored in VCS repository. This will enable team members to see the differences between versions of the same file, and they will know the time of the changes as well as the responsible team member. Furthermore, Development can be spit into different branches, each branch, lets say keeping track of the fixes associated with a software release. Then file versions can be obtained with a branch and can be applied to the same fix to multiple branches. Another benefit is that, VCS repository can be useful to understand how good the project was: How many lines changed from the previous version? Which are the most and least productive days of the week? Which team member made the most contribution? [7]
References
[1] Bazaar v2.1 Documentation
[2] A Brief History of VCS
[3] SCCS - The POSIX Source Code Control System
[4] The Source Code Control System by Marc J. Rochkind
[5] Source Code Control Systems
[6] Tichy, Walter RCS-A system for Version Control
- Version Control Systems,” by Diomidis Spinellis (IEEE Software, vol. 22, no. 5, 2005, pp. 108–109)