title: Does git-flow merging scale well for larger teams?
body: <p>We're considering to adopt git-flow in a team of ~10 developers with weekly release schedule. Our plan is to branch a release branch from develop every monday and stabilize it by next monday's release to production. In the meantime, multiple features can land in develop and so it will most likely be necessary to resolve merge conflicts between develop and release branch.</p>
  
  <p>Since the person doing the merge cannot possibly know all of the codebase and resolve conflicts by themselves, I'm wondering if this is going to cause problems. Basically, that person will need to talk to each of the developers and have them help resolve the conflict. I'm afraid this can be a bottleneck and become pretty tedious and painful.</p>
  
  <p>Is this a problem in practice? Any experiences merging branches in git-flow style of work? Or some other branching strategies with similar benefits?</p>