通过分支执行最佳实践
我对使用 perforce 有点陌生，想知道我应该/不应该做什么...... 我对分支的想法没有太多经验，我发现自己正在浏览标签以查找过去的版本和错误修复。
顺便说一句，我当前的设置是 Perforce 2009.1 和 Visual Studio 2008。
提前致谢！
I'm a bit new at using perforce and was wondering what I should/shouldn't do...
I don't have too much experience with the idea of branching out and I find myself looking through labels for past versions and bug fixes.
By the way my current setup is Perforce 2009.1 and visual studio 2008.
Thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
一般的分支策略是为主线创建一个分支，为开发创建一个分支，为每个版本创建一个分支。每个分支都允许另一条开发线。这个想法是，将针对发布分支进行错误修复，然后反向集成或“合并”到主线/开发中。最终，在下一个版本中，开发将集成到主线等。
对于分支/集成，要记住的最好的事情是始终保持与分支的父/子关系，除此之外，集成同级分支可能会导致计算成本高昂。
这有帮助吗？
The general branching strategy is to create a branch for mainline, a branch for dev and a branch for each release. Each branch allows for another line of development. The idea is that bugfixes will be made against the release branches, and then reverse integrated or "merged" into mainline / dev. Eventually, on a next release, dev will be integrated to mainline, etc.
The best thing to keep in mind with branches/integration is to always maintain a parent/child relationship with branches, going beyond that and integrating sibling branches can be computation expensive.
Does that help?
除了 Blaskovicz 所说的之外，我还可以推荐 Perforce 手册。
Besides what Blaskovicz said, I can also recommend the chapter on Codelines and Branching in the Perforce Manual.
一位 Perforce 顾问编写了一个相当简短的演示文稿，称为 Perforce Directory Standard，其中给出了用于不同风格的开发和发布维护的分支模型的非常具体的示例。
https://www.perforce.com/blog/100607/perforce-directory -标准-pds
A Perforce consultant wrote a fairly short presentation called the Perforce Directory Standard, which gives pretty concrete examples of branching models to use for different styles of development and release maintenance.
https://www.perforce.com/blog/100607/perforce-directory-standard-pds
您可以在《实用 Perforce》一书中找到许多有关充分利用 Perforce 的有用指南： http://shop.oreilly.com/product/9780596101855.do
You'll find a number of helpful guidelines about getting the most out of Perforce here in the book Practical Perforce: http://shop.oreilly.com/product/9780596101855.do