Too many releases on project page

We are filtering on "active" API versions for the whole site. Drupal.org has those enabled all the way back to 4.7.x; probably because no one knows about that configuration or is scared to uncheck those boxes (I know I am). What we are missing is filtering on whether the module's major version is supported.

I think I'll add a supported field to releases, which will be updated along with the security status.

The alternative is adding back views integration for the project_release_supported_versions table, which has one row per major version per project. (It doesn't fit neatly into fields because it is not per release.)

Thanks for investigating this.

I know it's another JOIN, but I think I prefer exposing the supported versions table instead of denormalizing supported into a field on releases. Don't we already need that to know/show which branch is recommended? But, if that becomes a rat hole for some reason, I'm okay with the new field, too.

Thanks,
-Derek

A JOIN isn't a problem, a field would be a separate table anyway. It is custom Views integration vs. custom setting field values. I actually think the custom Views integration might be best since it can be forward ported from D6.

This is done now. I did re-add views integration for project_release_supported_versions.