[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Best practise with tagging
From: |
Xanana Gusmao |
Subject: |
Best practise with tagging |
Date: |
Thu, 7 Oct 2004 06:49:48 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
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.
Thanks
Xanana
- Best practise with tagging,
Xanana Gusmao <=
- RE: Best practise with tagging, Paras jain, 2004/10/07
- RE: Best practise with tagging, Alastair Growcott, 2004/10/07
- RE: Best practise with tagging, Jim.Hyslop, 2004/10/07
- RE: Best practise with tagging, Jim.Hyslop, 2004/10/07
- RE: Best practise with tagging, Jim.Hyslop, 2004/10/12