RE: Best practise with tagging

[Jim.Hyslop]

Xanana Gusmao wrote:
> I am compiling a short list of best practise for CVS usage 
> especially for
> someone who's is the build engineer. Assuming that the source 
> tree compiles and
> passes all tests and is basically ready to be deployed to 
> production, I am
> recommneding that:
> 
>   "Before any public release of the software, you must tag 
> the module."
> 
> What do you think of it ? Basically tagging makes it easy to 
> compare changes
> between different releases. Any comments welcomed.
Tagging is good. Don't limit yourself to production tags, though. Any build
sent to QA should have its own tag, unless your shop is very small (i.e. one
person developing and testing).

Tags are cheap. Use them freely.

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.com/experts)