title: Gitflow with multiple master branches
body: <p>While this is similar to the thread <a href="https://stackoverflow.com/questions/16562339/git-flow-and-master-with-multiple-parallel-release-branches">Git-flow and master with multiple parallel release-branches</a> and to <a href="https://stackoverflow.com/questions/13653272/whats-best-way-to-work-with-git-on-multiple-master-branch">What&#39;s best way to work with git on multiple master branch?</a>, it is not quite identical...  I did find this one is rather similiar: <a href="https://stackoverflow.com/questions/19356630/multiple-projects-with-same-git-master">Multiple projects with same GIT master</a>, but I want discuss my specific use case...</p>
  
  <p>The company I work for is in the process establishing policies and procedures for our Git work flow.  We want to use the "Gitflow" model as described in the article <a href="http://nvie.com/posts/a-successful-git-branching-model/" rel="noreferrer">http://nvie.com/posts/a-successful-git-branching-model/</a> or
  <a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow" rel="noreferrer">https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow</a> and is commonly referenced in many discussions on the matter.</p>
  
  <p>We have a use case, however, with a requirement for which I cannot find a solution documented.  What if your project is used to produce more than one final product?  The master branch cannot therefore represent the "release points" as if it were one single product.  It seems that perhaps alternate branches are required from the master?  So multiple parallel release branches?</p>
  
  <p>For instance, what if the project acts as a backbone or engine to something that can have different skins, flavours, or variations but you want to have each of the full resulting final products stored in one repository?</p>
  
  <p>In my particular scenario, I have a program which runs on a Linux server, but it is also distributed as a local Windows application.  In these differing versions, there are large chunks of the project which may or may not be included in one or the other releases.  As an example, there are libraries on the server which do not need to be included if the repo was for the server only, but which must be included for the local distribution where they would not otherwise exist.  I want to pull updates to the repo onto the server at specific release points, but omit such pieces that don't belong there. </p>
  
  <p>From the master branch, would I create a "Server Release" and "Local Release" branch?  </p>
  
  <p>Where would the development branch (and it's features) then come off of?  I don't want multiple development branches, each coming from it's own release, as the code developments are in fact 99% applicable to both of those.  Do I need to merge a single dev branch into one and then the other release?</p>