[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Best practise with tagging
From: |
Paras jain |
Subject: |
RE: Best practise with tagging |
Date: |
Thu, 7 Oct 2004 12:52:47 +0530 |
There is already a document published for CVS best practices(look at that also,
good one):
http://www.magic-cauldron.com/cm/cvs-bestpractices/
Best Regards
Paras
-----Original Message-----
From: Xanana Gusmao [mailto:address@hidden
Sent: Thursday, October 07, 2004 12:20 PM
To: address@hidden
Subject: Best practise with tagging
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
_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs