title: Master Branch for Multi-Version Project (Git Flow)
body: <p>We're working on an application that is being used by multiple customers, each having a different version of the app.</p>
  <p>Our team is currently following the Git Flow branching strategy, but we've been hitting a wall on maintaining a single master branch.</p>
  <p>For example:</p>
  <ul>
  <li>Customer A has v1.1.2</li>
  <li>Customer B has v1.1.4</li>
  </ul>
  <p>We have fixed a vulnerability for Customer B in v1.1.4, and updated the version to v1.1.5 in the master branch.
  Now Customer B has asked for the patch fix in their version, but does not wish to update to v1.1.4 as of yet.
  This fix then gets versioned as v1.1.2.1 (still on its release branch).</p>
  <p>We are currently maintaining multiple release branches and pulling in feature branches in as needed, but we feel this isn't scalable in the long-run.</p>
  <p>Is there a recommended solution or branching strategy for this?</p>