View source for History of version-control systems (Wiki textbook Team4)

<p style="font-size:15px">                   
"<i>A source code system is a giant UNDO key-a project-wide time machine</i>"

							                                                -Andy Hunt and Dave Thomas 
<br/>



= 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 [http://www.informit.com/authors/bio.aspx?a=AFAC0A13-A141-47D6-B508-04A03D7B4634 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 [http://www.ipd.uni-karlsruhe.de/~tichy/ 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=

CVS , while using RCS underneath, is a lot more powerful tool and can control a complete source code tree. It can be greatly customized with scripting languages like PERL, Korn and bash shells. 

CVS offers the following significant advantages over RCS:
*	It can run scripts which you can supply to log CVS operations or enforce site-specific polices.
*	CVS enables developers from different geographical location to function as a single team. Information is stored on a single central server and the client machines have a copy of all the files. The client- server connection must be up to perform CVS operations but need not be up to edit or manipulate the current versions of the files. 
*	It can merge changes from non-CVS vendor branches.
*	Allows more than one developer to work on the same file at the same time
*	CVS servers run on most OS including unix-variants, Windows and OS/2 etc


=SVN=

Subversion is the next-in-line of  version control system. CVS has a number of problems, primarily caused by its dependency on the RCS file format for versioning files. These and other issues addressed by Subversion include the following.
*	In CVS, atomicity is not guaranteed. Subversion ensures atomicity.
*	CVS has no way to rename files and save versioning history. In Subversion, the common history of file1 and file2 is conserved.
Additionally, Subversion can be used for versioning a lot of different things. Directories and file metadata, as well as renamed or copied files, all have their own versioning.
*	In CVS, branching and tagging are expensive operations for big repositories and directory trees, which have a cost proportional to the number of files being branched or tagged. Subversion has made both branching and tagging constant time operations. They are implemented simply by copying the directory being tagged. 
*	CVS is not binary file friendly. Any change to a binary file results in the replacement of the old file. Subversion uses a different approach to provide efficient binary diffing which means it can store pdfs and other binary files efficiently. 
*	If we change a file locally using CVS, and we want to know the difference, then the entire file has to be sent to the server. When we change a file using Subversion repository, a copy of the latest repository revision is made locally. The differences are sent in both directions, which mean a lot less use of bandwidth.


=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].  

= 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? [8]

== References ==

[http://doc.bazaar.canonical.com/bzr.2.1/en/user-guide/introducing_bazaar.html] Bazaar v2.1 Documentation

[http://code.google.com/p/pysync/wiki/VCSHistory] A Brief History of VCS

[http://sccs.berlios.de/] SCCS - The POSIX Source Code Control System

[http://basepath.com/aup/talks/SCCS-Slideshow.pdf] The Source Code Control System by Marc J. Rochkind

[http://en.wikipedia.org/wiki/Source_Code_Control_System] Source Code Control Systems

[http://www.cs.purdue.edu/homes/trinkle/RCS/rcs.ps] Tichy, Walter RCS-A system for Version Control

[http://en.wikipedia.org/wiki/Revision_Control_System] Revision control System

[http://www.computer.org/portal/web/csdl/doi/10.1109/MS.2006.32] Version Control Systems,” by Diomidis Spinellis (IEEE Software, vol. 22, no. 5, 2005, pp. 108–109)