分支和合并策略
我正在寻找有关 .net 项目的分支和合并策略的信息。我一直在与其他开发人员讨论最佳实践方法，并且想阅读该主题。
例如，我们有 Main/Head，它是源代码的主要源树。为分支创建发布分支，并在适当的情况下合并到主分支。开发分支是为工作片段创建的，并与主分支合并。我正在寻找最佳实践策略、该做和不该做的指南等。
我们的源代码控制是 TFS2008。
关于这个主题的任何链接或文章都会很棒吗？
I am looking for information on branching and merging strategies for .net projects. I have been discussing best practice approaches with other developers and would like to read up on the topic.
For example, we have Main/Head which is the main source tree of source code. Release branches are created for branches and merged to main where appropriate. Development branches are created for pieces of work and are merged to and from main. I am looking for guidelines to best practises strategies, do's and dont's etc.
Our source control is TFS2008.
Any links or articles on this topic would be great?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
最好的起点是 ALM Rangers 制作的分支指南，最新版本适用于 TFS 2010，但它适用于 2008 年。如果您将软件构建为产品，那么该指南非常好，如果您正在构建内部软件，那么我建议放弃服务包分支的想法。
The best place to start is with the branching guidance produced by the ALM Rangers, the latest version is for TFS 2010 but it's applicable to 2008. If you're building software as products then the guidance is very good, if you're building in house software then I'd suggest droping the idea of a service pack branch.