Module filter or sort by release should impact what information is displayed

It has a finely published 6.x-dev snapshot: http://drupal.org/node/264339 Whether snapshots show up on the project pages are subject to per-project settings by the maintainer. So this module does have a 6.x release node, it is just not shown on the project page. It is shown when you go to all releases. Retitling to reflect the new findings.

But this works same as before the upgrade, and I personally like it this way..

Could that be a new filter? Something like:

Filter by release:
Stable release
Official release
Release shown on the project page
Any release

Now that #378830: Have core version facet impact the active/available sorts is done and deployed, the next step is cleaning up this UI problem. However, I think it's too limited to consider the -dev snapshot case. Really, we should reconsider displaying the download table at all on these pages. If you look at the current iteration of the d.o redesign prototype for module browsing pages, you'll see that Mark doesn't currently display any information about releases. I think that if you're sorting by "Latest release" (official) or "Recent activity" (-dev snapshot) it should display something like the date of whatever you're sorting by for each project. Obviously, if you're filtering by core, these values should be specific to the version of core you're filtering by.

Also, while we don't need the full download table, I think it'd be useful to display data about all the versions of core a module or theme supports. Damien and I were just discussing some kind of visual language used throughout the site for core versions, e.g. a little "6" or "7" icon that could be reused on these project browsing summaries, handbook pages, forum posts, whatever.

Moving this to a more appropriate queue so it's easier to find based on what actually needs to happen here.

Linking this from the Redesign project #661692: Meta issue for modules Project and Project issue tracking because this issue was tagged 'drupal.org redesign'

adding more redesign tags

@drumm: This isn't done. Here's an example:

- Filter by Drupal 7
- Sort by 'Latest release'

You'd expect to see modules sorted by their latest D7 release. Instead, you see any module that has a D7 release (even if it's a -dev snapshot that hasn't been updated in 3 months), ordered by their latest release for any version.

Another example: filter by core and then order by usage -- should order by the usage for the version of core you're filtering on. Etc.

That's how filters should interact with sorts.

There's also a question of the actual data displayed. I.e. if we're going to keep a download link or table, and you filter by a core version, the release for *that* core version should be displayed, etc.

The basics of this now work as desired. This orders by the latest D7 release while filtering to only those projects with a D7 release.
An example:
http://drupal.org/project/modules?filters=drupal_core%3A103&solrsort=ds_...

There are a few issues when shifting from one release to another in terms of selected sort method, but I believe that can be cleaned up separately.

Perhaps we should update the issue summary to reflect what remains to be done or discussed:

From comment #3:
"I think it'd be useful to display data about all the versions of core a module or theme supports."

From comment #8:
"filter by core and then order by usage -- should order by the usage for the version of core you're filtering on."
+1 from me on this one.

Anything else?

I also would like to have functionality describe in comment #8

or as describe in this dublicate issue
#1248932: Download & Extend pages: filter by compatibility and sorting by "most installed" should work together

I think the only remaining task of this issue is to solve the problem described in the duplicated issue linked to in comment #11:
If I am searching for most popular (i.e. "most installed") Drupal 7 modules, I wouldn't expect to find CCK, ImageAPI and jQuery UI (the last two don't even have a recommended D7 release) on top of that list.

It's not such a big problem for me, but for people new to Drupal, I guess it is highly confusing information.

I am closing this issue, as Drupal 6 is no longer supported.