Have the dev version information in the .info file so that modules can still be enabled when they have (2.x) in their information file. This just helps with working with git checkouts of the module. Very minor point, and doesn't affect any users. Just helps developers who checkout with git, and then are working with drush... Yeah, useless, but helpful to lazy people like me.
The actual version number gets overriden when it's packaged by Drupal.org.
Example:
name = xCSS
description = Empowers a straightforward and object-oriented workflow when developing complex CSS.
core = 7.x
dependencies[] = libraries (2.x)
Without 7.x-2.0-dev defined in libraries.info, when you have a git checkout of Libraries, you can't enable the xCSS module.
Comments
Comment #1
robloachHoly wrong patch file, Batman!
Comment #2
sunI think this is currently fixed for drupal.org:
#1314180: Make dev release numbers useful
...which should resolve Drupal core:
#1013302: Composer metadata on dev versions doesn't work in update.php
Also, admin_menu did this in the past, but now sees reasonable complaints:
#1251232: Unable to show correct version at admin/reports/updates if managed by Git
Comment #3
robloachYeah, let's wait off on this.
Comment #4
tstoecklerI think this is won't fix per http://drupal.org/node/542202#version
Otherwise we should update the docs over there.