Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!oliveb!ames!think!redsox!campbell
From: campbell@redsox.bsw.com (Larry Campbell)
Newsgroups: comp.software-eng
Subject: Re: Source Code Control
Message-ID: <791@redsox.bsw.com>
Date: 25 Jun 89 03:27:52 GMT
References: <597@pegasus.ATT.COM>
Reply-To: campbell@redsox.UUCP (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 23

I'm not too familiar with SCCS, but with RCS it seems that you could
use the "state" field to identify product versions.  For instance,
if we're going to make a snapshot/baselevel of the source library and
call it V1.01.02, we could do:

	rcs -sV1.01.01 RCS/*

Later, if we decide that a bug fix to foo.c needs to be considered
part of (backed in to) that baselevel, we just:

	rcs -sV1.01.01 foo.c

To build the baselevel:

	co -sV1.01.01 RCS/*
	make

We've just started using RCS and haven't actually tried this yet, but it
seems like it should be a serviceable approach.
-- 
Larry Campbell                          The Boston Software Works, Inc.
campbell@bsw.com                        120 Fulton Street
wjh12!redsox!campbell                   Boston, MA 02146