> --- [EMAIL PROTECTED] wrote:
> > However there is much momentum (culture and automated build scripts)
> > that take advantage of PVCS "promotion groups" which are like
> > constrained, floating tags. (They are constrained in the choices the
> > developer can chose from, such as Dev, Test, Staging, Prod).
> >
> > Is there any way to simulate this in CVS?
The "floating" part's easy; see the -F option to "cvs tag".
I don't know about the "constrained" part. CVS doesn't do that
out of the box, but perhaps it can be enforced using one of the
CVSROOT/*info files.
On Thu, Jan 16, 2003 at 06:38:57AM -0800, Kyle Adams wrote:
> We're also debating about ways to keep track of previous versions
> tagged for each environment. We'd like to do this to provide rollback
> functionality [...]
You could set two tags, a floating one for the scripts and a
non-floating one for the humans, e.g. "Test" and "Test-20020115"
respectively; or else set only the non-floating tag, and use some
mechanism external to CVS to tell the scripts which tag
corresponds to the current test build.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
