Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!xadmx!Leisner.Henr@xerox.com
From: Leisner.Henr@xerox.com (Marty)
Newsgroups: comp.unix.questions
Subject: Using RCS for release management
Message-ID: <18261@adm.BRL.MIL>
Date: 31 Jan 89 18:19:54 GMT
Sender: news@adm.BRL.MIL
Lines: 30

We're currently using RCS (actually MKS RCS on Ms/Dos) to manage a software
project with about 10 subdirectories and 150 files producing about 10
different executables/libraries in our system.

We're using RCS to track versions during development and it works
effectively.

What we want to accomplish is:
	1) an automatic way of generating a release where a common ident string
reflects the release level  (this isn't revision numbers of each source
file) -- only one magic release string should be generated per delivered
binary.
	2) What's the best way to extract the source code components of a release
at a later date.  It seems we can extract by date, symbolic name (assuming
one's assigned at release creation).
	3) Do we want to use the first digit of the revision number to make each
release?  This seems somewhat awkward, but will work to a limited extent.
So release 1.0 will contain revisions 1.xx, release 2.0 will consist of
versions at the 2.xx level, etc.  

Any better ideas?  We have access to RCS on Unix-based machines also so we
aren't limited to DOS-only ideas.
	
	
marty
ARPA:	leisner.henr@xerox.com
GV:  leisner.henr
NS:  martin leisner:wbst139:xerox
UUCP:	hplabs!arisia!leisner