in reply to Handling production code with source control, any better ideas?
We use subversion now, but back when we were using CVS, we always tagged releases with product_major_minor_patch. So instead of cvs upd with an existing tag we would take a current snapshot of the branch with cvs tag. Then we would export to the production environment by selecting files with the new release tag. That way we always knew what files went together even when we had to move files around for the next release.
|Replies are listed 'Best First'.|
Re^2: Handling production code with source control, any better ideas?
by suaveant (Parson) on Mar 16, 2011 at 20:48 UTC