old dev release marked as "Up to date"

I was able to reproduce this on a test site. After a little debugging, I discovered it was actually a misconfiguration of the nodequeue 6.x-2.x-dev release node. ;)
http://drupal.org/node/95884/revisions/view/306726/367507
It used to have its major version listed as "6" and its patchlevel as "2", but that'd correspond to version 6.x-6.2. The only reason this wasn't automatically done right is that administrators need to mess with the old "HEAD" release nodes and convert them into a release with a real version. This is a manual process, and therefore, error-prone.

So, update.module was confused by this release, and that's why it wasn't properly being marked as needing an update. Now that I fixed the release node and regenerated the XML file for nodequeue's release history that update.module reads, all is working as expected.

Cheers,
-Derek

p.s. I added a cautionary note to Associating old "HEAD" releases with a real version for site maintainers pointing to this issue. ;)

Thanks for the quick weekend action on this, Derek and for the report, Pasqualle!

@Derek: FYI, I can still configure the display settings for the non-existent 6.x-6.2 release, though these changes have no effect. I discovered this because the development snapshot disappeared from the project page until it was reconfigured.

I'll be sure to double-check version #'s next time I create a dev release node ;).

@ezra-g: Oh yeah, good point. Now fixed in the DB with this:

DELETE FROM project_release_supported_versions WHERE nid = 38678 AND major = 6;

Cheers,
-Derek