[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 09:19:26 +0200 |
> -----Ursprüngliche Nachricht-----
> Von: address@hidden
> [mailto:address@hidden Im
> Auftrag von Xanana Gusmao
> Gesendet: donderdag 7 oktober 2004 8:50
> Betreff: Best practise with tagging
>
> "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"
Since a tag does not always result in a branch...
A branch would be better in this case if you need to fix a bug in the
release and you cannot do it on the main trunk because some heavy
development has been done introducing new features that the original release
was not supposed to have.
Guus
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004
- Best practise with tagging, Xanana Gusmao, 2004/10/07
- AW: Best practise with tagging,
Guus Leeuw jr. <=
- 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