Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!nrl-cmf!ukma!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!amanue!oglvee!norm
From: norm@oglvee.UUCP (Norman Joseph)
Newsgroups: comp.unix.questions
Subject: Re: SCCS version control
Message-ID: <441@oglvee.UUCP>
Date: 12 Dec 88 16:16:45 GMT
References: <9125@smoke.BRL.MIL>
Distribution: na
Organization: Oglevee Computer Systems, Connellsville, Pa
Lines: 30


From article <9125@smoke.BRL.MIL>, by gwyn@smoke.BRL.MIL (Doug Gwyn ):

> In article <3217@ingr.UUCP> markv@ingr.UUCP (Mark VandenBrink) writes:
>>In developing a product under SCCS, we have, finally, gotten to the point
>>where we need to make a release.  So far no problems; however, I would like
>>to "remember" or baseline our platform so that some later time (fixes release,
>>etc.) I can automagically recreate the platform.
> 
>                     ... run a massive find on the source tree and for
> each SCCS archive, do a "get -e", remove the archive, and "admin -i" a
> replacement archive with SCCS ID 1.1.  Something similar but not so
> drastic could then be done for subsequent releases ...

If the version levels of all your source files are of the form `1.*',
you may also try doing a `get -e -r2' followed by a `delta'.  This
will bring the version level of all your source up to `2.1', which
you may consider a baseline.  At the next release, use `get -e -r3', etc.

If you follow this approach after using Doug's suggestion, you should
have a history of baseline releases of the form `1.1', `2.1', `3.1'...
Intermediate bug fixes and mods will have in-house version levels of
the form `<release>.<level>' where `<level>' is > 1.

Norm

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*//////////////////////////////////////
 Norm Joseph                   | UUCP: ...!{pitt,cgh}!amanue!oglvee!norm
 Oglevee Computer System, Inc. | "Everything's written in stone, until the
 Connellsville, PA  15425      |  next guy with a sledgehammer comes along."
/////////////////////////////////////*\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\