TFS:标签与变更集 [英] TFS: Labels vs Changesets

问题描述

我正在尝试提出有关使用TFS源代码管理的最佳实践.现在，无论何时进行构建，我们都会使用版本号将已签入的文件标记到TFS中.与仅检查文件并在注释中包含版本号相比，此方法更好还是更坏? 然后，如果需要，您可以使用变更集返回上一步吗?还是标签的用途更加广泛?

I am trying to come up with best practices regarding use of TFS source control. Right now, anytime we do a build, we label the files that are checked into the TFS with the version number. Is this approach better or worse than simply checking the files in and having the version number in the comments? Can you then use the changeset to go back if necessary or the labels are still more versatile?

谢谢！

推荐答案

它们有两个不同的用途，ChangeSet是文件实际更改时的状态，而您希望保留该更改的永久记录.标签标记文件的特定版本，以便您可以轻松地回到这一点.除非您的构建实际上在源代码控制下更改文件，并且您希望记录这些更改.您应该在贴标签.

They have two different purposes, ChangeSets are when the files have actually changed and you wish to keep a permanent record of that change. Labels mark a certain version of the files so that you can easily go back to that point. Unless your build actually changes files under source control and you wish to record these changes. You should be labeling.

此外，标签的资源消耗要少得多.而且，您可以在文件的同一版本上使用多个标签.

Also, labeling is much less resource intensive. And you can have multiple labels on the same version of a file.

这篇关于TFS:标签与变更集的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！