CSC/ECE 517 Fall 2009/wiki1a 4 SCM: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Source Code Management is a mechanism to track and store the modifications made to files during large scale software development. This is achieved by assigning a unique version number (also called revision number) for changes made to a file. Along with the version number, it also stores the username who made the changes, time-stamp and comments from the user. | |||
Version control provides a suitable environment for distributed, collaborative software development as it supports Version Comparisons, Restorations, and Merging etc. | |||
Some of the commercial Version control systems are [http://www.nongnu.org/cvs/ CVS], [http://subversion.tigris.org/ SVN], [http://git-scm.com/ Git], [http://mercurial.selenic.com/wiki/ Mercurial], [http://bazaar-vcs.org/ Bazaar], [http://dev.libresource.org/ LibreSource], [http://www.monotone.ca/ Montone], [http://www-01.ibm.com/software/awdtools/clearcase/ Clearcase], [http://www.perforce.com/ Perforce] etc. | |||
__TOC__ | __TOC__ | ||
Revision as of 21:56, 7 September 2009
Source Code Management is a mechanism to track and store the modifications made to files during large scale software development. This is achieved by assigning a unique version number (also called revision number) for changes made to a file. Along with the version number, it also stores the username who made the changes, time-stamp and comments from the user. Version control provides a suitable environment for distributed, collaborative software development as it supports Version Comparisons, Restorations, and Merging etc.
Some of the commercial Version control systems are CVS, SVN, Git, Mercurial, Bazaar, LibreSource, Montone, Clearcase, Perforce etc.