Labeling best practices?

Hi All,

I am just putting this out as a general question to solicit other peoples ideas regarding labeling. How do you do it (not as in how do I make TFS create a label) but rather, do you create a label after every build? Only when there are major releases? Do you label at the root only or recursively on each file? etc...

Cheers,

Clint

[367 byte] By [clintsinger] at [2007-12-20]
# 1
Clint,

I prefer to label as part of the automated build process for every build - taking it recursively from the point that the build was taken (i.e. $/TeamProject/trunk/Product ).

The main reason for doing it every time is to make it easy to track down what version of a file was in use for a particular build (for when bugs get raised etc). It also means that we can branch from any labeled build at any point in the future should (for example) build 1.0.0.1275 become a release.

I tend not to use labelling for anything else at the moment, but in previous projects where branching has not been used as heavily we would also label releases as well as builds.

Hope that make sense.

M.

MartinWoodward at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

Visual Studio Team System

Site Classified