drush inconsistent about dev release selection when user specifies a partial version (e.g. views-5.x, drupal-5.x).

I have found some inconsistencies with dev release selection in drush. The question is, if there is a dev release and an rc release, but no recommended release, should the dev release be recommended, or should the rc release be recommended? I could not find the appropriate page in the drupal.org manual, but drush is inconsistent in its interpretation.

For example, with Drupal 7, drush says:

$ drush pm-releases drupal-7.x
------- RELEASES FOR 'DRUPAL' PROJECT -------
Release Date Status
7.x-dev 2010-Dec-15 Development
7.0-rc2 2010-Dec-11 Supported, Security

$ drush dl drupal-7.x --drupal-project-rename=web
Project drupal (7.x-dev) downloaded to /home/ga/work/web.

This could be okay, because there is no recommended release, so the most recent release is taken instead. Should drush skip the latest dev release, though?

Here is what drush does for Drupal-5:

$ drush pm-releases drupal-5.x
------- RELEASES FOR 'DRUPAL' PROJECT -------
Release Date Status
5.x-dev 2010-Aug-11 Development
5.23 2010-Aug-11 Supported, Recommended, Security

$ drush dl drupal-5.x
Project drupal (5.x-dev) downloaded to /home/ga/work/drupal-5.x-dev.

This does not look right; there is a recommended release, but drush is taking the dev release.

Drush seems to get it right for modules:

$ drush pm-releases views-5.x
------- RELEASES FOR 'VIEWS' PROJECT -------
Release Date Status
5.x-1.x-dev 2010-Nov-12 Development
5.x-1.8 2010-Jun-16 Supported, Recommended, Security

$ drush dl views-5.x
Project views (5.x-1.8) downloaded to /home/ga/work/views.

So far I think this is only a problem when the user specifies a partial version number (e.g. -5.x).

Maybe this is not very important... workaround: use --select if drush picks the wrong version.