Administer releases: Bogus release 6.x-0.x-dev marked as recommended

If you only have one release for a branch, then if it's supported, then it's also recommended. (by design)

The other issue seems a little odd since there doesn't appear to be any releases other than 6.x-1.x-dev (published or unpublished) and no tags in cvs...

I'm not sure I understand the problem. Even though your 0.x branch is marked as recommended, you have no releases for that branch. Since you have also marked your 1.x branch as supported, and have ticked the "Show snapshot releases" box for that branch, your 1.x snapshot release is listed in the download table.

For development snapshots, the download table does not say anything about being supported. If a developer only has one branch, the developer can create an actual release from that branch and that will be marked as recommended in the official releases table. If there are no official releases, the developer can untick the "Show snapshot releases" box for that branch and nothing will be shown in the download table.

As dww pointed out in the devel list (http://lists.drupal.org/pipermail/development/2008-March/029109.html), in some cases the upgrade might not have made the smartest decision of what values to use for your module. In your case, even though you don't have a DRUPAL-6-1 branch for your module, HEAD is essentially a branch and since you have a 6.x-1.x development snapshot based on HEAD, that's a release. I'm setting this to by design because I don't think there is a problem here. If you still think there is, please try to be a little more clear about what you expect to see and how what you are seeing now is different from your expectation.

Pretty sure this is a bug in the DB update that entered bogus entries into the {project_release_supported_versions} table for some reason. I'm doing a little DB digging now to see if I can get to the bottom of it, and hopefully just repair it all automatically. Stay tuned.

Argh! :(

So, a month ago when someone accidentally upgraded d.o before all this stuff was ready, d.o was running the wrong code and was clobbering values in the {project_release_default_versions} table. There are 401 projects that have a bogus entry in there with major version 0. So, during the DB update last night, the update code saw these bogus entries and converted them into rows in the new {project_release_supported_versions} table. Boo hoo. :(

Therefore, I guess I have to work out some funky SQL to find bogus entries in {project_release_supported_versions}, remove them, and fix up the other entries that might now be invalid due to not having a supported/recommended version. Ugh.

I fixed this yesterday and emailed devel, I just forgot to close this issue.