Mercurial、Branch 解决方案中的每个项目？
目前，我们使用 Mercurial 作为 BitBucket 上的 VCS。
该项目现在的方式是一个解决方案，所有代码都签入在“默认”分支上工作的所有开发人员。每天早上，我们都会创建一个构建版本并由 QA 负责。
我想知道对每个开发人员单独进行分支是否更有意义，因为每个开发人员都在解决方案中处理一个项目。
另一个要点是这将如何影响 QA？他们需要在构建之前合并所有分支吗？
我对此真的很困惑。
Currently, we're using Mercurial as our VCS on BitBucket.
The way the project is right now, is a solution with all the code checked in with all the developers working on the "default" branch. Every morning, we create a build release and the QA have it.
I'm wondering whether it makes more sense to branch each dev on his own since each dev is working on a project in the solution.
The other main point is how would this affect the QAs? Would they need to merge all the branches prior to building?
I'm really confused about this.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
正如“何时应该创建分支”中提到的，您可以使用分支来隔离开发工作。
在您的情况下，您将隔离您正在处理的解决方案中的每个项目。
这将允许：
，但这还需要合并到一个公共分支中，以便将所有项目作为解决方案一起进行测试。
请参阅 HgInit（来自 Joel Spolsky），了解有关此类协作工作流程的更多信息。
在“存储库架构”中，Joel 说明了两个不同团队中隔离的两项开发工作，但仍然包括同步（合并）最后的努力。
As mentioned in "When should you make a branch", you use branching to isolate a development effort.
In your case, you would isolate each project in the solution on which you are working.
That would allows for:
But that would also require a merge in a common branch for all the project to be tested together as a solution.
See HgInit (from Joel Spolsky) for more on that kind of collaboration workflow.
In "Repository Architecture", Joel illustrates two development effort isolated in two different teams, but still including a synchronization (merge) effort at the end.