-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Guus Leeuw jr.
Sent: Thursday, October 07, 2004 11:12 AM
To: [EMAIL PROTECTED]
Subject: AW: Best practise with tagging
Von: Jim.Hyslop [mailto:[EMAIL PROTECTED]
Guus Leeuw jr. wrote:
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
Title: AW: Best practise with tagging
Err - you don't want to
branch every release, just major releases. Minor releases presumably do not
involve any major changes in functionality.
Here at my company we tag every potentially
public release (even though testing often means they never get
Guus Leeuw jr. wrote:
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
Before any public release of the software, you must tag
the module.
I would suggest Before any ... You must branch the module
with a release
tag
I disagree.
Branches can be very complex to manage. I
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
