Question

RCS (Revision Control System), a configuration management tool, adopts a reverse delta approach for storing multiple versions of a file. To optimize storage, RCS only stores the latest version of each configuration item and the differences between each version. For example, assume a file has three revisions—1.1, 1.2, and 1.3. RCS stores the file as of version 1.3, then the differences between 1.2 and 1.3, and finally the differences between 1.1 and 1.2. When a new version is created, say 1.4, the difference between 1.3 and 1.4 is computed and stored, and the 1.3 version is deleted and replaced by 1.4.

Do you think RCS is able to apply Version Control in this case? List the pros and cons of this tool as a configuration management tool. Also, suggest some other tool that could be used for this scenario.

Answer 1

Revision Control System

In my point of view and based on the research I have done, RCS can be used in the case which you have menioned. Up-to date history is available and you can retrieve and revert the older version of the docuent too.

Pros

Simple structure
Easy to work
saving is not reliant on a central repository
Cons

less security: version history can be edited by the users.
one user can work on a file at a time.
Other tools which can be used are

CVS

most popular and widely adopted revision control system.
simple system to keep files and revisions up to date.
There are many IDEs for CVS comprising Xcode (Mac), Eclipse, NetBeans and Emacs all of which use CVS.
Pros

It is a time-tested
Lot of IDEs that use CVS.
Cons

moving or renaming files will not include in the version update
symbolic links to files includes security risks
Very slow tagging and branch operation
Very little support for binary files
SVN

widely adopted version Control Systems.
Open-source projects such as Ruby, Python Apache, etc. use it.
Pros

New and improved system
allows atomic operations
Branch operations are easier and inexpensive
Several IDE plugins are available
Cons

has bugs when files and directories are renamed
The commands are not enough to manage repository
slow compared with other systems
Mercurial

Effective for larger projects where many developers and designers are involved.
High-performance system posing optimum speed.
simple and extensive documentation.
Pros

Low-learning curve
Extensive and better documentation
Highly distributed model
High-performance system with great speed
Cons

more extension than scripting
Not allow out-of-the-box operations
Bazar

Offers easy and flexible user experience.
Can be used with distributed code base.
Pros

Offers a more innovative and detailed set of commands, quality IDE support
customizable feature set perfect for a range of projects.
Cons

New and not mature enough as a version control system
Lacks IDE support like robust systems such as CVS or SVN.