title: Git Workflow and Release Branches: Many, One, or None?
body: <p>For our web development, we have daily to weekly deployments.  There are instances where we deploy something to QA, but they don't get around to testing it for a few days, and then we have a production fix or a new enhancement that needs to go out.  Two questions:</p>
  
  <p>(1) What would be a good workflow for this?</p>
  
  <p>(2) What are the advantages and disadvantages to having one continuous, long lived branch called production or release, as opposed to a new release branch for each release, or just doing everything out of master and tagging it accordingly?  Again, this is for web development with frequent releases that can get backed-up.</p>