title: Doctrine 2.5.11 introduces problems on PHP 7.0
body: <p>Today was updating an server installation and broke my whole setup. Noticed that doctrine/orm ~2.5.6 loaded 2.5.11 which requires </p>
  
  <ul>
  <li>Installing doctrine/collections (v1.5.0)</li>
  <li>Installing doctrine/annotations (v1.5.0)</li>
  <li>Installing doctrine/common (v2.8.1)</li>
  <li>Installing doctrine/instantiator (1.1.0)</li>
  <li>Installing doctrine/orm (v2.5.11)</li>
  </ul>
  
  <p>doctrine/collections and all the other packages require PHP 7.1. Thats why my application was not working anymore. Upgrading to 7.1 was not an option for now so we fixed the dependencies to:</p>
  
  <p>, "doctrine/orm"                        :   "2.5.10"
  , "doctrine/annotations"                :   "~1.4.0"
  , "doctrine/collections"                :   "~1.4.0"
  , "doctrine/common"                     :   "~2.7.0"</p>
  
  <p>Now my question: <strong>Is the version number from doctrine/orm 2.5.11 not wrong? Shouldn't it be 2.6 since it requires dependencies which do not work in 7.0 and it will break installations?</strong></p>
  
  <p>The problem came up since (on Mac) the php version is different from the apache version. Thats why I think the semantics in the version numbering should be improved or the requirements in the doctrine/orm package need to be less loose.</p>
  
  <p>I am interested to understand how this can be done better from my side.</p>
  
  <p>Just for google will add the Exception message: Return value of Doctrine\Common\Annotations\AnnotationRegistry::registerFile() must be an instance of Doctrine\Common\Annotations\void, none returned</p>