title: When using semver when to upgrade/bump to 1.0.0 (stable)
body: <p>The Semantic Versioning Specification (<a href="http://semver.org/" rel="nofollow noreferrer">SemVer</a>) defines:</p>
  
  <blockquote>
    <p>Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.</p>
  </blockquote>
  
  <p>So starting with <code>1.0.0</code> is considered stable.</p>
  
  <p>When starting a project normally version <code>0.1.0</code> is used and gradually increased, there is a point where the project can have something like <code>0.20.3</code> for months/years and it is "stable".</p>
  
  <p>Therefore would like to know what could be considered good practices to follow besides the criteria, arguments before bumping a project to server <code>1.0.0</code>. </p>
  
  <p>How you are dealing with this?  </p>
  
  <p>If there are not issues/code activity in 3 months the version is dumped? </p>