title: Semantic versioning and git branches
body: <p>I have a master branch at <strong>v1.0</strong> and a develop branch that is <strong>v1.1dev</strong>.</p>
  
  <p>I then make a new release branch from dev, and bump the version number from <strong>v1.1dev</strong> to <strong>v1.1</strong>, finish up, merge said release branch into master, and presto - <strong>v1.1</strong> is born at <code>master</code>.</p>
  
  <p>But then, I merge the same release branch back into dev and so the dev branch is also <strong>v1.1</strong>.</p>
  
  <p>Although this is technically true, I feel like dev it should always end in <strong>dev</strong> since, after all, it is the development version that is working toward the next real version.</p>
  
  <hr>
  
  <p>So my question is:</p>
  
  <ul>
  <li>Does everyone dedicate a single commit on the dev branch to bump the version of their Dec code after merging in a release branch, or is there something I'm missing (a script, a methodology, a technique, etc.)?</li>
  <li>Also, is the above description generally representative of how people bump their version numbers?</li>
  </ul>
  
  <p><strong>TL;DR:</strong> <strong>When should you bump version numbers in the various branches of a git-versioned project assuming semantic versioning?</strong></p>