Source Control

[Stewart, Mark]

CMS...

Overview

    During development, team members continually make changes to project
    files.   CMS stores, keeps track of, and monitors these files (called
    elements).  CMS also lets you manipulate combinations of files within
    a library (called groups and classes).

    CMS stores project files in a central library where they are available
    to all project members.  Some of the functions you can perform using
    CMS include the following:

         (1) Store elements in a library for safekeeping

         (2) Retrieve elements, and modify and test them in your own
             directory

         (3) Control concurrent modifications to the same element

         (4) Merge concurrent modifications to a file

         (5) Create successive versions, or generations, of files

         (6) Compare two versions of an element within a library

         (7) Organize related library elements into groups

         (8) Define a set of various element generations (called a class)
             to make up a baselevel or release version of a project

         (9) Track which users are working on which files from the library

        (10) Maintain a historical account of element and library
             transactions

Taken from CMS help.

Mark Stewart
CTG Consultant
Victoria's Secret Stores
OpenVMS Alpha  V7.1-1H1
Oracle Rdb     V7.0-1
PowerHouse 4GL 7.10.F4



= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.