[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS and traditional source control
From: |
Stephen Rasku |
Subject: |
Re: CVS and traditional source control |
Date: |
Tue, 16 Jan 2001 09:49:55 -0800 (PST) |
Alan Weston wrote:
>
>Hello, I'm completely new to CVS and versioning so please be nice.
>How does one use CVS whilst maintaining the advantages of the more
>traditional approach of migrating code from a development environment
>once unit tested to a test environment for system and cycle testing
>and ultimatley to a release environment for actually using? My
>concern is about losing control of what goes into test and release
>and when it goes in there. As I've confessed this is all a bit
>new to me so I apologise if the question is, as I suspect, missing
>the point of versioning, if so please enlighten me. Many thanks in
>advance for your time.
>
>
You can accomplish what you want by branching and merging. I suggest
you read the CVS manual sections on these topics:
http://www.cvshome.org/docs/manual/cvs.html
Also, there is an excellent article on branching and merging here:
http://www.enteract.com/~bradapp/acme/branching/