[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AW: Best practise with tagging

From: Guus Leeuw jr.
Subject: AW: Best practise with tagging
Date: Thu, 7 Oct 2004 17:11:45 +0200

> Von: Jim.Hyslop [mailto:address@hidden 
> Guus Leeuw jr. wrote:
> > > -----Urspr√ľngliche Nachricht-----
> > > Von: address@hidden 
> > >   "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 recommend creating 
> them only when
> necessary. If you have a non-branch symbolic tag applied, it 
> is trivial to
> create a branch *when needed*.

True, but what about a person doing cvs tag release_1_0_0 and later (half a
year) cvs tag release_1_0_0?
CVS will tell the person that the tag already exists... If (s)he thinks to
be smart, (s)he might want to try cvs tag -f release_1_0_0 at which point
you loose your release revision and there'll be no way to bug fix the client
without feature upgrade.

Of course you can say people shouldn't be too silly, but things go wrong
when people work ;)

Is a branch really expensive and difficult to manage if you don't touch it


Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004

reply via email to

[Prev in Thread] Current Thread [Next in Thread]