SOURCE CODE CONTROL SYSTEM CODE MANAGEMENT SYSTEM

Source Code Control System Code Management System

The first Version Control System was created in 1972 at Bell Labs where they developed UNIX. Before we begin using the modern Version Control Systems, a little bit of history is worth looking at. Google Code even uses SVN as a way of exclusively distributing code.tually any text file - based version control or source code management system to control your code , this chapter covers VSS because it's the one I use. Most forms of open-source projects will use Subversion because many other large products such as Ruby, Python Apache, and more use it too. SVN, or Subversion as it is sometimes called, is generally the version control system that has the widest adoption.

Both SCCS and RCS only worked on the development system and were not for sharing code, as they only worked for a single user. Ten years later the Revision Control System, or RCS, was developed, and it was the first cross-platform version control system, but once again, it was only for text files. It was available only for UNIX and only worked with Source Code files.

Later on in the 1980s, along came Perforce, and it was widely used during the. It was still file-focused and kept track of changes in individual files, as opposed to keeping track of changes in entire directory trees. The Concurrent Versions System, or CVS, was the first one that had a central repository and was usable by multiple users.

TFS comes with an MSDN subscription, which means it's fairly expensive. In 2004, Microsoft created the Team Foundation Server to replace its aging Visual SourceSafe Version Control System, which was primarily a client server system. So you could check in an entire directory tree and check it out. In 2000, a new product called Subversion was created and supported non-text files, tracking directory structure changes, such as file renames and moves, and its transaction unit was the directory as opposed to an individual file.

Previously, they had a product which was used by Linus Torvalds and the kernel group on Linux that was called the Community Edition, and it was free. Distributed Source Code Control came about because of a change in licensing from a company called BitKeeper. Everybody shares their own individual repository and then can share their changes with a central server or share their changes with individual users. Distributed Source Code Control is different in that there's not a central server that everybody shares.

That's a short history of Version Control from 1972 to 2012. A competing product Mercurial was also created in 2005 in response to the same BitKeeper change and is also widely used in open source projects. It's broadly used in conjunction with something called GitHub which is an online cloud-based service which offers free hosting for open-source projects and also commercial hosting for private use.

And now that we have looked at the history, let's move on to looking at a little bit more details about the terminology that we need to understand, and a walk-through about how centralized and distributed systems work.