[Top][All Lists]

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

AW: AW: Best practise with tagging

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

> -----Urspr√ľngliche Nachricht-----
> Von: address@hidden 
> [mailto:address@hidden Im 
> Auftrag von Xanana Gusmao
> Gesendet: donderdag 7 oktober 2004 10:52
> Betreff: Re: AW: Best practise with tagging
> Guus,
> > I would suggest "Before any ... You must branch the module with a 
> > release tag"
> Yes that makes sense. Code release should come from a branch 
> which is the stable version of everything from HEAD. That 
> branch should be tagged. 
> The next question: In a tagged branch, is it advisable to 
> retag it ? What scenarios would force us to retag it? I think 
> it should be left alone indefinitely. All bug fixes on the 
> branch will sooner or later be merge back to the trunk.

Every time you do a merge from the branch back on the trunk, you need to cvs
tag -f branch_merged the branch , so you can upd -j branch_merged -j branch
the next bug fix to the trunk.


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]