tfs 2010 最佳实践
我们面临着一个非常棘手的情况，如果处理得当，肯定可以避免。
在我们的 TFS 2010 中，特定应用程序有 5 个不同的分支。所有分支都合并为 1 个分支，并且由于合并是由不属于开发团队的系统管理员完成的，因此我们最终清理了代码（添加错过了来自 3 个发生冲突的不同位置的更改）这相当于花费了近 2 周的额外努力来稳定代码分支并在进一步进行之前进行测试。
为了避免将来出现此类挫折，应该遵循什么最佳实践，因为我们对于在同一应用程序上运行的不同开发项目有多个代码分支。
we have a very tricky situation which am sure can be avoided if dealt with properly.
There were 5 different branches of a specific application in our TFS 2010. All the branches were merged into 1 branch and since the merging was done by a system administrator who wasn't part of the development team, we ended up cleaning the code (adding the missed changes from 3 separate places where ever they were conflicts) This amounted to almost 2 weeks of extra effort to get the code branch stabilised and tested before proceeding further.
What should be the best practice to be followed to avoid such frustrations in future as we have multiple code branches for different development projects running on same applications.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
请参阅 Visual Studio ALM Rangers Team Foundation Server 2010 分支指南。
See the Visual Studio ALM Rangers Team Foundation Server 2010 Branching Guide.