Branches are your solution. Create STAGE and PROD branches ( cvs rtag -b STAGE <modulename> ).
Keep developers working on new code in HEAD (main trunk), and have them commit fixes to STAGE branch (they'll have to check it out locally -- cvs co -r STAGE <modulename> ) At some point once STAGE branch is good to become PROD, backup old PROD (cvs rtag -b -rPROD OLD_PROD <modulename>) and then force STAGE code to PROD branch (cvs rtag -b -rSTAGE -F PROD <modulename>). In order to create new STAGE force latest HEAD code STAGE branch (cvs rtag -b -F STAGE <modulename>) Don't forget that prior to creating new STAGE -- PROD needs to get merged back to HEAD: cvs co <modulename> cvs -q up -j PROD (there may be conflicts that will need to get resolved) -----Original Message----- From: Datla, Raghav [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 18, 2001 12:38 PM To: '[EMAIL PROTECTED]' Subject: How can we maintain modules/directories/files between production and development environment using CVS 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?. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
