Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!darkstar!spica.ucsc.edu!timothy
From: timothy@spica.ucsc.edu (Timothy Oborne)
Newsgroups: comp.software-eng
Subject: To SCCS or to RCS, ...
Message-ID: <308@darkstar.ucsc.edu>
Date: 20 Jul 89 22:45:21 GMT
Sender: usenet@darkstar.ucsc.edu
Reply-To: timothy@spica.ucsc.edu (Timothy Oborne)
Organization: University of California, Santa Cruz
Lines: 28

Looking for advice:

	Should I stick with SCCS because it comes standard on all
	of our development platforms (UNIX of various flavors)?

	or

	Should I attempt to acquire, port and maintain RCS on 
	our growing number (3 now, ?? more ) of different UNIX 
	platforms?

	(Are the benefits of RCS worth the trouble?)
	
We are a small workgroup of 4-6 programmers working of a medium/large
scale software system.  The source for the system will be developed on 
multiple architectures.

Any references to papers on management of a similar collection of source 
code would be greatly appreciated.

Please e-mail responses.  I will summarize for the net.

Thanks in advance,

=========================================================================
Timothy W. Oborne, Systems Programmer	INTERNET: timothy@spica.ucsc.edu
University of California, Santa Cruz	UUCP: ucbvax!ucscc!saturn!timothy
=========================================================================