20-CMS - Change Version Management A look at CVS Subversion and cfengine What is Version Management Management of multiple revisions of the same

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Change / Version  Management A look at: CVS, Subversion and cfengine
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
What is Version Management? Management of multiple revisions of the same unit of information Application Source Code, Art Resources such as blueprints or electronic models SCM (Software Configuration Management) - Revision control for software projects
Background image of page 2
Why is it important? Teamwork Allows for information to be worked on by a team of people concurrently “copy-modify-merge” model Prevent overwriting of someone else’s change Development Develop two versions of the software concurrently Fix minor bugs in a stable version while adding bleeding edge features to another Debugging Retrieve and run different versions of the software to determine in which version(s) the problem occurs Provides accountability, who made what change when
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
SCM Packages Server Based CVS Subversion Rational Clear Case (proprietary) Distributed GNU Arch Git – Used for Linux kernel development BitKeeper (proprietary) Many Others
Background image of page 4
CVS Concurrent Versions System CVS developed from an earlier versioning system called Revision Control System (RCS) The code that eventually evolved into the current version of CVS started in April 1989 CVS is extremely popular, and it does the job.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CVS Terminology Module A single project managed by CVS Repository Where a CVS server stores the modules it manages Checking out Acquiring a copy of a module Working copy The checked out files Committing Updating the repository with the changes you made on your working copy Update Acquire the latest changes from the repository in the working copy
Background image of page 6
CVS Problems Number of awkward limitations Changes are tracked per-file instead of per- change Commits aren't atomic Renaming files and directories is awkward Must be deleted and re-added Branching limitations Some of the maintainers of the original CVS have declared that the CVS code has become too crusty to effectively maintain.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Subversion Background Designed specifically to be a modern replacement for CVS Don’t need to break new ground in version control
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/06/2008 for the course CSE 265 taught by Professor Davison during the Spring '08 term at Lehigh University .

Page1 / 29

20-CMS - Change Version Management A look at CVS Subversion and cfengine What is Version Management Management of multiple revisions of the same

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online