与外包团队合作的分支策略？
我计划管理一个在我的代码库上工作的外包开发团队，让该团队在功能分支中完成分配给他们的所有工作。他们将负责每周合并来自主干的更改。我自己的团队也会根据需要继续使用功能分支。
根据使用特定分支策略集成外包工作的经验，有人有任何建议吗？
I am planning to manage an outsourced dev team working on my codebase by having that team work in feature branches for all the work they have been assigned. They would be responsible for merging changes from the trunk weekly. My own team would also continue to use feature branching as required.
Does anyone have any tips based on experience integrating outsourced work using a particular branching strategy?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
根据我的经验，与外包开发团队合作时，最好避免涉及太多手动步骤的开发流程。如果对如何解决合并问题存在困惑，那么他们将不得不将此问题传达给您或您的内包团队的成员，这会减慢每个人的速度。
我接触过的大多数外包团队都在印度，所以时区差异是一个挑战，他们的工作日通常在你的工作日结束时结束，除非你有一个在东部时间、中部、太平洋山区时间工作的昂贵团队。沟通问题简直是致命的，大多数时候我第二天会发现他们一无所获，因为如果没有我的直接帮助，他们无法解决问题。
合并通常是不受欢迎的，但我个人只看到它在由中级到高级开发人员组成的紧密团队中发挥作用。
It has been my experience that when working with outsourced development teams it is best to avoid development processes that involve too many manual steps. If there is confusion about how to resolve a merge issue then they will have to communicate this to you or a member of your insourced team and that will slow everybody down.
Most outsourced teams I have dealt with were in India so you have the time zone difference as a challenge, their work day usually ends when yours begins unless you have a pricey team that works EST, central, mountain pacific times. The communication issues are just killer and most of the time I would come in the next day to find they accomplished nothing because they couldn't figure something out without my direct help.
Merging is generally frowned upon but I have personally only seen it work in close knit teams with intermediate to senior developers.