将后备箱更换为架子是否明智？
我们目前正在从 SVN 迁移到 TFS；
如今，有主干、分支和标签来跟踪和组织我们的开发。但是，当我们有搁架组时，我们质疑是否需要行李箱，并且可以搁置待处理的活动并取消搁置和取消搁置。根据需要将它们合并到主分支中。
这是一个好的计划吗？这样做会产生不良后果吗？以前有人尝试过吗？
提前致谢！
We're currently migrating from SVN to TFS;
Today there are Trunks, Branches and Tags to track and organize our development. But we are questioning the need of a trunk while we have shelvesets, and could just shelve the pending activities and unshelve & merge them as necessary into the main branch.
Is it a good plan ? Are there bad consequences upon doing this, has anyone tried before ?
Thanks in Advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您没有行李箱的理由是什么？
当您有变更集时，“主干”上没有历史记录。尽管您可以从一个搁置集进行构建，但不可能从多个搁置集进行构建（从而验证组合的开发工作）。
这也非常危险，你可能很容易失去轨道。
尽管有可能，但我永远不会走那条路。您在 TFS 源代码管理中进行了分支，该分支运行良好。为什么要尝试模拟这种分支？
要查看有关分支的良好指南，请参阅 Visual Studio TFS 分支指南 2010
What is your rational for not having a trunk?
When you have changeset, there is no history on the 'trunk'. Although you can build from a shelveset, it is not possoble to build from multiple shelvesets (and thus validate a combined development effort).
It is also very risky and you could loose track very easy.
Altough it might be possible, I would never ever go for that route. You have branching in TFS Source Control, which works perfecly. Why trying to simulate this branching?
To see good guidance on branching, see Visual Studio TFS Branching Guide 2010