TOC PREV NEXT INDEX DOC LIST MASTER INDEX




More on Summit/CM Version Control (Apex/Summit)

Placing a file under version control tracks the file's development by saving a version of the file every time it is checked in. Each version is a snapshot of the file's contents at a given time.

Checking out a file begins the process of making a new version of the file. You can modify a controlled file only while it is checked out.

When you check in the file, the new version is completed and the file becomes read-only.

Creating multiple versions of a file produces a time-ordered, numbered sequence of versions called a version history (or just history). You can visit any version in a history (use Control > Show > Versions (Apex/Summit)), but you cannot modify a version.

Although you cannot modify a version, you can use the contents of any version as the basis for creating a new version.

Version control is described in detail in the Summit User's Guide.

Additional Topics

For additional information, click on a topic:


Rational Software Corporation 
http://www.rational.com
support@rational.com
techpubs@rational.com
Copyright © 1993-2001, Rational Software Corporation. All rights reserved.
TOC PREV NEXT INDEX DOC LIST MASTER INDEX TECHNOTES APEX TIPS