[comp.os.vms] Configuration Management System for a VAX 11/780

gkazz%jplpds.span@VLSI.JPL.NASA.GOV (08/04/87)

The Planetary Data System Project at the Jet Propulsion Lab is currently
evaluating configuration management systems (CM systems) for its VAX 11/780.
The Project is small: 15 developers writting a maximum of 30K lines of code.

The features we desire in a CM system are:

1. Provide controlled access to subdirectories on the VAX in configuration
libraries which can store source, object, executables, and binary file types.

2. Provide history information on the files in the configuration library such as
who modified what, when and why.

3. Provide for recreation of previous versions.

4. Provide status reporting on baseline builds.

5. Define file dependencies between source-source code, source-obj.,
source-include, and include-include files.

We have looked into DEC's CMS and are concerned about the performance issues
of that product. If any of you have any experience with CMS or can comment
on the performance of CMS on your system, or know of any other CM system more
applicable please send your comments to:'

         JPLPDS::GKAZZ%JPLPDS.SPAN@JPL-VLSI.ARPA
Thanks.

tencati@VLSI.JPL.NASA.GOV (08/05/87)

Please note that the return address Greg gave in his recent message to 
info-vax is incorrect.  The correct address to send replies to his query is:

               GKAZZ%JPLPDS.SPAN@JPL-VLSI.ARPA

Also note that he is not a regular subscriber to info-vax and will not see any
messages that are sent to the list.


Ron Tencati
System Mgr/Postmaster
JPL-VLSI.ARPA (VLSI.JPL.NASA.GOV)