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:[EMAIL PROTECTED] Sent: Thursday, October 07, 2004 12:20 PM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
