once the new release system goes live, and releases are real nodes (http://drupal.org/node/83339), the existing "view all releases" page is going to start to get quite huge and unwieldy. one easy (and consistent from a UI perspective) partial solution would be to add the identical "Filter by version" drop-down selector at the top of the page, just like we have on the module browsing pages.

Comments

merlinofchaos’s picture

A couple of possibilities I see here:

Use a table format similar to sourceforge -- which presents a *very* readable table of versions.

Break the table up into Drupal release versions, and keep development snapshots separate from real versions. List real versions in version # order. So something kind of like this:

+---------
Drupal 4.7
+----------
1.0-beta [info][download]
1.0-rc [info][download]
1.0 [info][download]
2.0 [info][download]
short version of the teaser here because this is the 'current' version'
+---------
1.x-dev [info][download]
2.x-dev [info][download]
+---------

Repeat for 5 and 6 etc. Go ahead and include the filter at the top of the page, though tabs (or fake tabs) are probably just as useful and easier (maybe) to deal with.

Then include HEAD at the very end.

Possibly automatically only include the 2 or 3 most recent API versions and 'collapse' the rest, possibly linking to another page to get that info.
|

dww’s picture

that comment would have probably been better in http://drupal.org/node/89537.
all i'm talking about here is the identical:

Filter by Drupal Core compatibility: [4.7.x] (go)

UI that you see at the top of http://drupal.org/project/Modules ...
(since it'd be trivial to re-use the same code that adds that little version filter).

aclight’s picture

Version: 4.7.x-1.x-dev » 5.x-1.x-dev
Status: Active » Postponed

I'm not quite sure I understand the feature request. Is this to have a version selection box on the list of releases for a specific project, such as at http://drupal.org/node/48429/release

If so, this should be easy to do with views, since we'll probably create those pages using views anyway. Therefore, I'm setting this to postponed.

dww’s picture

Version: 5.x-1.x-dev » 6.x-1.x-dev
Status: Postponed » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.