Xref: utzoo comp.software-eng:557 comp.unix.wizards:8448 comp.sys.att:3220
Path: utzoo!attcan!uunet!steinmetz!davidsen
From: davidsen@steinmetz.ge.com (William E. Davidsen Jr)
Newsgroups: comp.software-eng,comp.unix.wizards,comp.sys.att
Subject: Re: More SCCS usage/Has anybody heard of "SABLE"?
Keywords: SABLE, SCCS, configuration management
Message-ID: <10835@steinmetz.ge.com>
Date: 13 May 88 18:07:36 GMT
References: <647@vsi.UUCP> <503@ace.UUCP>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 29

There is a technique I use for keeping things in line with SCCS. Perhaps
it's widely know and not used for some reason, but here it is.

Assume I'm at a production level, say 1.1, and am ready to make another
upgrade. First I pull an initial branch of all the files:
	for n in s.*; do get -b $n; done

Now when I want to change something I do:
	get -e -t s.whatever
which keeps things moving along the branch. When I delta I add comments
as always.

When I'm ready to update to the next production level (which in this
case will be 1.2) I just do:
	for name in s.*
	do
	 get -e -t -r1.1 $name
	 delta -y"Production version" $name
	done
This will force all programs to have a version of 1.2, even if they
weren't changed.

I do the intermediate access with a script which does an extract if
there is no writable version, asks if I want to edit, asks if I want to
make, etc. Not elegant, but simple, easy to use, and reliable.
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me