Re: Control tagging of labels Test, QA and Production?

[Andy Jones]

Allow me to suggest a simpler alternative.

Developers do not book code into CVS until it is ready to be promoted to QA.  
Presumably you would not want code included in the automatic build unless the 
developers had completed it, so your "test" tag works fine as it is.

Tested QA code is then tagged with a release tag once it has passed QA; you can 
then easily release using 'export -r <release tag>'.

Regrettably there are few safeguards to stop developers tagging in ways that 
they should not.  But it should not be difficult to find out who created a 
given tag, so it's just a matter of keeping your eyes open.