[epp-dev] Role, importance, or use of pre-req feature versions?

[David M Williams <david_williams@xxxxxxxxxx>]

I know that the latest versioning guidelines recommend not to use "require 
features" at all, except in some special circumstances, but instead to let 
the bundle pre-reqs to sort themselves out in P2. 
http://wiki.eclipse.org/index.php/Version_Numbering

I think an epp package is clearly one of special circumstances ... to 
'require' at least the minimum set of highest level features. 

Given that we should "require features", what should we do about the 
version numbers there? 

Leave them off? Is the "highest available in repository" used then? 
Put in the current release ones, and use "compatible" matching rule (the 
default). Is there any performance gain to add this extra constraint? Or 
... a performance penalty? 

Such as ... 

   <requires>
      <import feature="org.eclipse.cvs" version="1.1.0"/>
      <import feature="org.eclipse.equinox.p2.user.ui" version="1.1.0"/>
      <import feature="org.eclipse.help" version="1.1.0"/>
      <import feature="org.eclipse.jdt" version="3.5.0"/>
      <import feature="org.eclipse.platform" version="3.5.0"/>
      <import feature="org.eclipse.rcp" version="3.5.0"/>

      <import feature="org.eclipse.mylyn.ide_feature" version="3.2.0"/>
      <import feature="org.eclipse.mylyn.java_feature" version="3.2.0"/>