From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3c8a1ddc13ecb354
X-Google-Attributes: gid103376,public
From: Ken Garlington <garlingtonke@lmtas.lmco.com>
Subject: Re: Configuration Management for Ada on Unix
Date: 1996/06/04
Message-ID: <31B409D7.41A4@lmtas.lmco.com>#1/1
X-Deja-AN: 158437561
references: <9605301407.AA03821@most> <qw6u3wytapf.fsf@gargantua.enst.fr>
content-type: text/plain; charset=us-ascii
organization: Lockheed Martin Tactical Aircraft Systems
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.01 (Macintosh; I; 68K)
Date: 1996-06-04T00:00:00+00:00
List-Id: <comp.lang.ada>


James A. Squire wrote:
> 
> To me, one of the aspects of a CM product should be that one of the many
> objects it operates on is called "baseline" - and this should be a
> separate construct apart from branches or labels or whatever.  It's
> cleaner and safer.

If it's important to you, you might want to look at Product Configuration
Management System (PCMS) from SQL*Systems. It has an explicit "baseline"
construct, separate from the concept of "variants". The newer versions of
PCMS also add a "work package" concept that may be of interest.

-- 
LMTAS - "Our Brand Means Quality"