[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: Best practise with tagging
From: |
Xanana Gusmao |
Subject: |
Re: AW: Best practise with tagging |
Date: |
Thu, 7 Oct 2004 08:52:28 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
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.
Thanks
Xanana
- Best practise with tagging, Xanana Gusmao, 2004/10/07
- RE: Best practise with tagging, Paras jain, 2004/10/07
- RE: Best practise with tagging, Alastair Growcott, 2004/10/07
- RE: Best practise with tagging, Jim.Hyslop, 2004/10/07
- RE: Best practise with tagging, Jim.Hyslop, 2004/10/07
- RE: Best practise with tagging, Jim.Hyslop, 2004/10/12