New Post: Identify an artifact or Multiple Artifacts for a Project

Hi all,

In TFS I understanding there is the branching and the labeling but it also seems with TFS that it's too much information or risky, respectively.

Assuming we have a multiple applications comprised in 1 team foundation collection (TKC) and they total comprise 2000 artifacts:

If we have a project that let's say only changes 6 of those 2000 artifacts and 2 developers working them:

• Creating a branch works BUT it branches off the main and thereby makes a copy of the 2000 artifacts so the 6 can be changed and isolated. That would utilize a lof of unnecessary space for changing just 6 artifacts BUT it would work.
• Creating a label works BUT labels are free-form text and meaning each developer could label it with a different name.
  

A code-promotion type branching model sounds reasonable off the Main to QA and release for stabilization but what is the best method to isolate and identify the changes to those 6 artifacts in this example?

If there was a way to promote and identify without a label (due to the risk) that is ideal but I am not seeing it with TFS nor did I with VSS.

Any assistance and inforamtion on this would be greatly appreciated.