Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!cs.umn.edu!kksys!edgar!brainiac!apertus!news
From: ivanp@mc.UUCP (Ivan Peters)
Newsgroups: comp.software-eng
Subject: CVS-RCS
Message-ID: <1991May21.135016.3671@apertus.uucp>
Date: 21 May 91 13:50:16 GMT
Article-I.D.: apertus.1991May21.135016.3671
Sender: news@apertus.uucp (0000-news(0000))
Reply-To: apertus!ivanp@tenfwd.uci.com
Organization: Apertus Technologies
Lines: 27

I am looking over CVS, a system that is a add on to RCS (a configuration
management system) and I have a question I hope someone would please answer:

How does CVS support (or does CVS support) dual derivations?

example:
If someone is deveolping on release 2, of something, and someone else
is developing on release 1.  How does one make release 1.1, 1.2, etc, 
(a branch) while allowing work to continue on 2.1 2.2?   These releases
contain multiple files and sub-dirs.

(assume test is the top directory in the repository)

One can tag a release.       (cvs tag -rTEST2_0 test)
One can checkout a release.  (cvs co -rTEST1_0 test)
One can update from a release.    (cvs update -rTEST1_0 test)

One can not check in a release, other than the most current. (cvs ci *)

Is there a easy process that I am missing? 
How do others do it?
I would like to avoid making a new dir under the repository for each 
release to be worked on if possible...

Any help would be REALLY APRECIATED!!!!!

Thanks in advance. :-)