创建＆QUOT;标签＆QUOT;在颠覆说明文件应在下一版本中有什么 [英] Create a "label" in subversion indicating what files should be in the next release

问题描述

我一直在使用版本控制了一段时间的StarTeam，但我搬到颠覆。我一直在阅读颠覆书，并似乎有一个主要功能的StarTeam有颠覆没有按'笔 - 标签的概念。我知道Subversion有标签，但他们意味着什么在StarTeam不同。在StarTeam中，我可以标注一组文件，如准备建立，然后只检查那些出来，包括特定版本。然后，我可以创建一个冻结的标签，表明被列入该版本中哪些文件（类似于一个Subversion标签，但它是在那些特定的修订，在目录不是一切）。

I've been using StarTeam for version control for some time, but am moving to Subversion. I've been reading the Subversion book and there seems to one major feature that StarTeam has that Subversion doesn't - the concept of labels. I know Subversion has labels, but they mean something different in StarTeam. In StarTeam, I can label a set of files as "ready to build" and then only check those out and include in a particular release. I can then create a frozen label indicating what files were included in that release (similar to a Subversion tag, except it's on those specific revisions, not everything in the directory).

有没有办法在Subversion中获得这样的功能？我知道你可以指定打标签的修订，但在你有code和即将做了发布，并找到一个错误，或者有人决定一个特定的变化不应该包括在内的情况会发生什么。我知道你可以创建基于资源库和本地工作副本的标签，但是这涉及到检查出不应该被包括在内，创建标记文件的具体修改意见。随着准备打造标签，你不会把这个标签在头上的版本，你不想要的文件。似乎没有任何自动方式指定某些版本在Subversion的构建。这不是在那里的一个新功能应该在一个分支进行开发的情况下，但如果修订在树干（或任何你会从标签）更多，但不应该包括在内。它可能不需要被还原 - 的变化可能是合适的，但在将来的版本中，这不是当前。如果没有你所需要的确切文件版本特定的修订版本，好像你必须手动混合和从储备库的匹配和你的工作拷贝。

Is there a way to get such functionality in Subversion? I know you can specify which revision to tag, but what happens in the situation where you have code and are about to do a release, and find a bug, or someone decides a particular change shouldn't be included. I know you can create the tag based on the repository and your local working copy, but this involves checking out specific revisions of the files that shouldn't be included and creating the tag. With a ready to build "label", you wouldn't put that label on the head version of the files you didn't want. There doesn't appear any automatic way to designate certain revisions for a build in Subversion. This isn't the case where a new feature should be developed in a branch, but more if a revision is in the trunk (or wherever you will make the tag from), but shouldn't be included. It may not need to be reverted - the change could be appropriate, but in a future release, not this current one. If you don't have a specific revision with the exact file versions you need, it seems like you'll have to manually mix and match from the repository and your working copy.

在类似的情况，如果有什么的Subversion不属于释放的部分，不需要被标记的文件。在StarTeam中，你不会附上准备建立标签给他们，但在颠覆，似乎在目录中的一切。有没有一种方法来排除从构建和标签这样的文件？请问这是什么过滤流排除是

In a similar situation, what if you have files in Subversion that aren't part of the release and don't need to be tagged. In StarTeam, you wouldn't attach the ready to build label to them, but in Subversion, it seems everything in the directory. Is there a way to exclude such files from the build and tag? Is this what svndumpfilter exclude is for?

在短，是有办法只包含一个标签某些文件的具体修改，或者它必须是无论是在存储库中的特定修订，或文​​件的存储库中的手工组合和你的工作副本？

In short, is there a way to only include specific revisions of certain files in a tag, or does it have to be either a specific revision in the repository, or a manual mix of files in the repository and your working copy?

推荐答案

如果我正确地理解你的问题，我相信它可以在某些时候发布前分支（例如，在该点所有的主要功能来处理你要包含在此版本已经完成），然后小心地管理什么获取合并到了释放分支。 主干线是免费的，新的东西。例如，如果一个错误识别那么这可能是（一）固定在主干线和然后作出决定是否也应该合并到释放分支;或（b）固定在树枝上。这是我们遵循的过程，它工作得很好（但它确实也需要纪律和一定量的正式流程的）。

If I understand your problem correctly, I believe it can be handled by branching at some point prior to the release (e.g. at the point all of the main functionality you want included in this release has been completed) and then carefully managing what gets merged onto that "release" branch. The "main trunk" is free for new stuff. For example, if a bug is identified then this could be (a) fixed on the main trunk and then a decision is made about whether it should also be merged into the release branch; or (b) fixed on the branch. This is the process we follow and it works quite well (but it does also require discipline and a certain amount of formal processes).

这篇关于创建＆QUOT;标签＆QUOT;在颠覆说明文件应在下一版本中有什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！