title: dev-master in composer.json, is this madness?
body: <p>I'm using composer (in Symfony2 projects) and often get errors updating libraries.</p>
  
  <p>Many libraries (most to my experience) use dev-master as version for their dependencies (or worse they use * ). </p>
  
  <p>Whenever something is committed to the master branch you get to update the library, and the chances of an API change are higher as time goes by. What today in master is version 1.2.1 tomorrow could be 1.2.7, with no harm, and become later 1.7 or 2.x with sure incompatibilities.</p>
  
  <p>My questions are</p>
  
  <ol>
  <li>how did we get to this point? Is it a practice suggested from high profile sources?</li>
  <li>what can I/we do to sensibilize the authors to this subject?</li>
  </ol>
  
  <p>or
   am I mad?</p>