Re: Info-cvs digest, Vol 1 #1246 - 16 msgs

[Damian Wiest]

The short answer?  RTFM, pay attention to the discussion of tags and branches.  
Don't be afraid to experiment with things in a test repository.

Basically you want to cut a release branch when you're ready to start testing.  
Make any bugfixes prior to release on this branch and then tag the branch with 
the release name when your ready.  As bug reports come in, you can either make 
the fixes directly on the release branch, or create a bugfix branch off of the 
release branch and make your fixes there.  After you've tested the fixes, you 
can merge the changes from the bugfix branch back into the release branch (and 
trunk).

-Damian

>Message: 11
>From: "Datla, Raghav" <address@hidden>
>To: "'address@hidden'" <address@hidden>
>Subject: How can we maintain modules/directories/files between production 
>       and development environment using CVS
>Date: Tue, 18 Dec 2001 15:38:22 -0500
>
>Hi,
>  As a CVS administrator,  How can we maintain modules/directories/files
>when we have environments like production, stage and Development.
>I mean once Developers develop some code, test it and then I want to keep
>these files or code in the production cycle after testing is done.
>
>Can anyone please through some light on this?.