From owner-freebsd-questions  Sun Jun  9 08:37:23 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA28475
          for questions-outgoing; Sun, 9 Jun 1996 08:37:23 -0700 (PDT)
Received: from wdl1.wdl.loral.com (wdl1.wdl.loral.com [137.249.32.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA28458
          for <questions@freebsd.org>; Sun, 9 Jun 1996 08:37:20 -0700 (PDT)
Received: from miles.sso.loral.com (miles.wdl.loral.com) by wdl1.wdl.loral.com (5.x/WDL-2.4-1.0)
	id AA15004; Sun, 9 Jun 1996 08:36:49 -0700
Received: by miles.sso.loral.com (4.1/SSO-SUN-2.04)
	id AA10065; Sun, 9 Jun 96 11:35:02 EDT
Date: Sun, 9 Jun 1996 11:34:59 -0400 (EDT)
From: Richard Toren <rpt@miles.sso.loral.com>
X-Sender: rpt@miles
To: questions@freebsd.org
Subject: CVS setup used at FreeBSD?
Message-Id: <Pine.SUN.3.91.960609112406.9984A-100000@miles>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Gentlemen;
  I am looking at different available version/release control systems for 
a project that I am working on. I have never used source control, but am 
aware of the concept and such. 
  I started out with simple RCS; then a month ago I tried a simple instal 
of CVS on my home system. This weekend I am reading O'Reilly's "RSC & 
SCCS" which presents TCCS.
  Back to CVS. Since you folks use that to maintain control over multiple 
branch, distributed development systems; I thought seeing the way the 
control files are set up would give me a chance to to evaluate the 
complexity of managing CVS.
  My immediate environment is a distributed class interface library. 
There are 7 developers, 120+ objects (1/directory), 8 capability builds 
before delivery of release 1.0 on the first of 6 different platforms.
  My questions have to do with the following:
    > definition of 'modules' that cross directories.
    > creation of developer work areas for safe private work.
    > makefile philosophy that works is the workarea, beta area and 
       production.
    > release tagging and control.
    > ...
 Any help (examples from FreeBSD) would be appreciated.

                         ====================================================
Rip Toren               | The bad news is that C++ is not an object-oriented |
rpt@miles.sso.loral.com | programming language. .... The good news is that   |
                        | C++ supports object-oriented programming.          |
                        |    C++ Programming & Fundamental Concepts          |
                        |     by Anderson & Heinze                           |
                         ====================================================