RE: Best practise with tagging

[Alastair Growcott]

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 publically released), and we branch when we create a major new version. We currently have three branches. The currently available version that has been in use for ages, the new major version/upgrade that is still going through extensive testing and debugging before full release (I believe betas have already been publically released) and our mainline along which major development is still taking place.

 

We also tag a branch when we make a patch.

 

One reason for our tagging is because we build multi-platform software. If we create a build or a patch or a support pack for one system, and then later a customer wants it for antoher system we can build exactly the same code by using the tag.

 

However that's just the way we do it - check out Paras Jain's URL too.

 

---

From: [EMAIL PROTECTED] on behalf of Guus Leeuw jr.
Sent: Thu 07/10/2004 08:19
To: [EMAIL PROTECTED]
Subject: AW: Best practise with tagging

> -----Urspr�ngliche Nachricht-----
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] 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




_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet.
________________________________________________________________________

_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs