CSC/ECE 517 Fall 2011/ch1 1f sv

Comparing Version - Control Systems from the programmer's stand point

Version Control System (VCS) is a software used by a group of users simultaneously working on the same document, program, image or other information. This helps people to simultaneously collaborate with one another on a project without constantly having to swap files between them.This system lets the users track the changes made to the files over time, which means that at any point of time the users can roll back to a previous version of the file. The versions are usually identified by an incremental letter code known as a revision number. This helps go back to the last known good version of the file in case of errors. The changes made to the file are labeled with the name of the person who introduced it, time of the change and an optional description to track the evolution of the file over time.VCS also allows you to branch from the source file, create a parallel copy of the file, make your own changes and then merge the two files in the future.

Here we shall look at the different types of Version Control Systems available and a few examples of the same, discussing about their features and limitations from a programmer's stand point.

Overview

The concept of Version Control is gaining increasing ground with the increase in the number of Software development projects requiring a large group of programmers to develop onto the same source code. As many developers collaborate to develop new projects, it becomes all the more important to ensure consistency among the work being done and deployed. Besides enabling collaborative development, version - control also helps track and fix bugs in the source without the other parts of the project being affected. It is critically important when developers need to identify the root cause of a bug, by retrieving and running different versions of the project. Version-Control Systems range from a simple file based model where individual files are versioned to a distributed model where the entire repository is versioned.

In most cases,the programmers are geographically separated from one another and are working on different parts of the code and pursuing varied interests and goals.

Terminology

• Repository: A repository is the place where the current and historical data of the files under a project are stored, often on a server. It can either be of a file or centralized or a distributed model.

• Branch: When two or more developers intend to work on distinct copies of the file, those set of files under version control may be branched so that each of them can work independently on their own copy. The changes made to a filein a particular branch are not visible to the other developers unless they havebeen merged back.

• Trunk: The unique line of development that is not a branch. This is sometimes also known as the mainline.

• Tag: A tag or label refers to an important snapshot in time, consistent across many files. These files at that point may all be tagged with a user-friendly, meaningful name or revision number.

• Working copy: The working copy is the local copy of files from a repository on which the developer works, at a specific time or revision. Any changes to be done to the repository are initially done on a working copy. Conceptually, it is a sandbox.

• Check-out: Creating a local working copy from the repository is called check-out. The developer may either check - out a particular revision of the file or just the latest.

• Commit: The act of merging the changes made in the working copy back to the repository is known as a commit or check-in.

• Merge: When two sets of changes are applied to a file or set of files, it is known as a merge operation.

• Promote: When the content of a file is copied from a less controlled location into a more controlled location, it is called as promoting.

Criteria for comparing the different Version Control Systems

Listed below are the criteria for comparing the different types of VCS:

General Properties

• The repository model: describes relationship between the various copies of the source code repository.
• The concurrency model:describes how can simultaneous edits to the working copy can be done without stepping on ther users feet.
• Platform: specifies the operating system that the software supports.

Technical Properties

• Scope of change: describes if changes are recorded on a file basis or a directory basis.
• Version IDs: describes if version number is based on hashed content of the file, or sequential numbering of files etc.

Features

• Atomic commits: ensures either all the changes are committed or none are.
• File renames: describes if the software allows files to be renamed while retaining their version history.
• Merge file renames:describes if the software can merge changes made to a file on one branch into the same file that has been renamed on another branch.
• Symbolic links: describes if the software allows version control of symbolic links as with regular files.
• Merge tracking: describes if the software tracks the changes which have been merged between respeictive branches and only merges the changes that are missing when merging one branch into another.

Types of Version Control Systems

The version control systems can be classified into three categories:

1. Local version Control

In the local-only approach, all developers must use the same computer system. These softwares often manage single files individually and are largely replaced or embedded within newer software.

General Properties of Local Version Control

• It employs a file server repository model, maintaining multiple copies of the same file.
• Checksums and deltas are employed to maintain file integrity
• It was basically developed for the UNIX Operating Systems.

Technical Properties of Local Version Control

• It versions only individual files.
• Versioning is achieved through a sequential numbering of the files.

Examples of Local Version Control

Source Code Control System

Source Code Control System (SCCS) is an early version control system and is a part of UNIX. SCCS is now obsolete and is replaced by Revision Control System. It is based on interleaved deltas, and 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.

Features of SCSS

• SCCS provides facilities for storing, updating and retrieving all versions of modules by version number.
• It records the change, time of change, user who did the change and location of change.
• It helps retrieve an earlier version of the file in case of system crashes or unintended deletion of the file.

Limitations of SVCC

• It versions only individual files, therefore it is suitable only for small projects consisting of single developers.

Revision Control System

Revision Control System

Revision Control System(RCS)is a software used to manage multiple revisions of a file. For text that is edited frequently RCS is used for automating the storing, retrieval, logging, identification, and merging of revisions.

Features of RCS

• Mulitple copies of the same file are maintained.
• RCS stores deltas.

Limitations of RCS

• It is error-prone, due to many copies of the same file.
• It is advantageous with a single developer working on the project. Multiple developers needs administrative intervention for maintenance of files.
• Built - in locking mechanism is made use of when several developers are working on the same project, instead of branching individual files as the syntax for branching of files isvery cumbersome.

2. Centralized Version Control

The Centralized Version Control, also known as the Client - Server model, consists of a single shared repository which acts as the server and the users are the clients. The repository is located at one place and provides access to all the clients for making changes, commits and sending and receiving information.

General Properties of the Centralized version Control

• It employs a client-server (centralized) repository model.
• It employs a merge concurrency model.
• It runs on Windows, MAC and UNIX - like Operating Systems.

Technical Properties of the Centralized version Control

• Changes made to the files are recorded on a file basis.
• Sequential numbering of files is used for versioning.

Examples of the Centralized Version Control

Concurrent Versions System

Concurrent Versions System (CVS) was originally built on Revision Control System and is licensed under the GPL.It uses a client–server architecture in which clients connect to the server where the current versions of a project along with its history is stored and "check out" a complete copy of the project, make changes to this copy and then later "check in" their changes. The client can establish a connection with the server either over a LAN or the Internet. CVS also provides facility for client and server to run on the same machine if the version history of a project is limited to be tracked with only local developers.

The Concurrent Versions System is an important component of the Source Configuration Management.

Features of CVS

• Several developers can work concurrently on the same project, each one "checking out" files of the project within their "working copy", and "checking in" their changes to the server.
• In CVS the client can continue to work on the checked out copy even if the network between the client and the server is disconnected.
• The problem of users stepping on others feet is avoided as the server allows users to "check-in" to the most recent version of the file.It is therefore expected of the developers to keep their working copy up-to-date by incorporating other people's changes on a regular basis.
• On a successful check - in, the version numbers of all the files are incremented and the copies are updated with a user supplied description line, author’s name and the time.

Clients can also compare versions, request a complete history of changes, or check out a historical snapshot of the project as of a given date or as of a revision number.CVS labels a single project (set of related files) which it manages as a module. A CVS server stores the modules it manages in its repository. Programmers acquire copies of modules by checking out. The checked-out files serve as a working copy, sandbox or workspace. Changes to the working copy will be reflected in the repository by committing them. To update is to acquire or merge the changes in the repository with the working copy.

Limitations of CVS

• Revisions created by a commit are per file, rather than spanning the collection of files that make up the project or spanning the entire repository.
• CVS does not version the moving or renaming of files and directories.
• Versioning of symbolic links is not enabled.
• Limited support for Unicode and non-ASCII filenames.
• Commits are not atomic.
• Branch operations are expensive.

Subversion

Subversion (SVN) is an open-source, Apache License versioning control system inspired by CVS and is available on the major operating systems.

"Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations."

Features of SVN

SVN provides developers with the following advantages when compared to legacy CVS:

• All commits are atomic operations.
• Full revision history is maintained for files renamed/copied/moved/removed.
• Versioning is maintained for directories, renames, and file metadata which enables developers to move and/or copy entire directory-trees while retaining the entire revision history.
• Versioning of symbolic links.
• Branching as a cheap operation, independent of file size.
• Files which cannot be merged, are locked by developers which is known as "Reserved checkouts".

The transaction model is employed by the Subversion filesystem to keep changes truly atomic. A transaction operates on a specified revision of the filesystem, not necessarily the latest. The changes are made on the root of the transaction, which when committed becomes the latest version, or is aborted.Several developers can access the same transaction and work together on an atomic change.

Repository types and Branching

SVN offers two types of repository storage :

• FSFS and
• Berkeley DB.

SVN employs the inter-file branching model of trunks, branches and tags to handle versioning.

The 'svn copy' command creates a new branch. This creates an old and a new version copy which are linked together internally and history is perserved for both. Only the differences between the copied and the original versions are stored in the respoistory, resulting in the copied version taking up only a small amount of space. The versions in a branch, maintain the history of the file till the point of the copy, and any changes made since. The changes made can be merged back into the trunk or between branches.

Limitations of SVN

• It does not have repository administration and management features.
• It does not store the timestamps of modifications.
• It stores additional copies of data on the local machine which can cause space issues for large projects.
• It does not provide support for merge of file renames.

3. Distributed Version Control

In Distributed Version Control Systems, instead of maintaining a centralized shared repository, the entire repository is maintained by the developers and the changes are shared between them on a peer to peer basis. This system emphasizes on sharing changes among peers rather than tracking, backing up and synchronizing changes.

If required a Distributed Version Control System can create centrally administered locations where the users update the changes. Though most of the times , the repository is independently maintained by the users. The users are not required to share the changes on a regular basis and can do so at their discretion.

General features

• Everyone maintains a personal sandbox, which maintains the incremental history and thus programmers are not required to log in to a central server.
• The Programmers are not required to be connected to the network at all times. Even if the server is down, the programmers can continue working from anywhere.
• The changes are made to the local repository and hence the commits and reverts are much faster than in a Centralized system.
• Every change made is given a "guid" or a Unique id, which makes it simpler for the system to track and share changes.
• The guids help in merging files without creating duplicates.
• The DVC's are easier to set up and manage. A perennially running server is not required to be maintained. Adding peers is not centrally administered and thus programmers can attach themselves to the system.

Limitations

• A central repository is not available in case the programmers loses data and needs to access the core data.
• There's no stable latest version of the code present centrally.
• There are no revision numbers, only change numbers and hence going back to a previous revision is not easy.

Examples of Distributed Version - Control System

Git

Git is a distributed version control system where the emphasis is laid on speed. In this, the working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. It comes with a simple design and offers strong support for non-linear development. It is fully distributed and can handle large projects like the Linux Kernel efficiently.

Git differs from the other types of version control systems in the way it thinks about its data. It thinks of its data more like a set of snapshots of mini file system rather than a list of file-based changes.

Git was originally designed to be a low level version control system engine to which others could code their front end. It has eventually grown into a complete revision control system which can be used directly by the programmers.

General Properties of Git

• Git employs a distributed repository model.
• Git uses a merge concurrency model.
• Git is primarily developed for Linux based systems, but runs also on UNIX - like operating systems, POSIX based systems and Windows.

Technical Properties of Git

• Version IDs are checksummed with SHA - 1 hash which is a 40 character string based on the content of the file.
• Git knows everything by hash and not by file name.

Features of Git

• All commits are atomic operations.
• Git provides partial support for file renames. It does not explicitly track file renames as it does not track individual files.
• Git provides support for merge file renames.
• Versioning of symbolic links is enabled.
• Everytime a commit is performed, Git takes a snapshot of the files.
• Files that have not been modified are not copied.
• All operations like browse history and commit are local.

The working copy of a developer is a mirror repository, called a Git clone and it is a complete repository with entire history and revision tracking capabilities. Such a repository is neither dependent on network access or a central server. This model enables branching and merging to be fast and easy to do.

The Three States

Git has three states in which a file can reside : Committed, Modified and Staged.

• Committed: Data is stored safely in the database.
• Modified: The file has been changed but not yet merged to the database.
• Staged: A modified file has been marked in its current version to go into the next commit snapshot.

Workflow of Git

Files are modified by the developer in the working directory and are then staged in the staging area, where snapshots of them are added. Once the changes are committed, the files are taken from the staging area and the snaphots are stored permanently in the GIT directory.

Mercurial

Mercurial is an Open Source Distributed Version Control Tool for software developers. It is programmed to be used on multiple platforms. Mercurial is a fast , lightweight and efficient tool for handling of very large distributed projects. Mercurial supports both personal projects as well as large Scale Enterprise level projects.

General Properties of Mercurial

• Mercurial employs a distributed repository model.
• Mercurial uses a merge concurrency model.
• Mercurial is supported on Windows and Unix-like systems, such as FreeBSD, Mac OS X and Linux.

Technical Properties of Mercurial

• Mercurial was mainly implemented in Python, but also includes a binary diff implementation written in C.
• In Mercurial revisions are identified using Hashes.
• Mercurial uses an HTTP based protocol which tries to reduce the round trip time, new connections and data transferred. It can also work over a similar protocol in SSH.

Features of Mercurial

• All commits are atomic operations.
• Mercurial provides support for File Renames
• Mercurial provides support for the merging of file renames.
• Mercurial provides symbolic links to create references to other files.
• Mercurial supports merge tracking.

References

[1]http://en.wikipedia.org/wiki/Revision_control

[2]http://en.wikipedia.org/wiki/Subversion_(software)

[3]http://en.wikipedia.org/wiki/Comparison_of_revision_control_software

[4]http://better-scm.berlios.de/comparison/comparison.html

[5]http://git-scm.com/

[6]http://progit.org/book/

[7]http://subversion.apache.org/

[8]http://expertiza.csc.ncsu.edu/wiki/index.php/CSC/ECE_517_Fall_2010/ch1_1a_br

[9]http://expertiza.csc.ncsu.edu/wiki/index.php/CSC/ECE_517_Fall_2010/ch1_1a_vc