Closed (duplicate)
Project:
Drupal.org site moderators
Component:
Site organization
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2012 at 23:42 UTC
Updated:
6 May 2014 at 15:22 UTC
Jump to comment: Most recent
Comments
Comment #1
dddave commentedClosing old issues that went stale or never got support.
Comment #2
liam morlandCan you explain what you mean by "went stale"? I still want this. What codes has to change to implement this? If it is public, I could probably write a patch.
Comment #3
dddave commentedTry catching tvn on irc #drupalorg or #drupal-infrastructure and discuss it with her. She should be able to give you some qualified guidance on this.
Comment #4
jweowu commentedThis is quite frustrating. It's very hard to get any visibility for a release candidate if it doesn't appear on the project page.
Given that dev snapshots are available (which are surely expected to be less stable in general), having the other releases listed as well seems highly desirable.
I guess the logic would be to select the latest release (using the standard version sorting; stable > rc > beta > alpha) for each major version, compare that with the stable release, and display it if they're different.
So if there's a release candidate for the next major version (after the current stable release), that rc would be displayed. And if there's no release candidate, but there's a beta release, then it would be displayed. Then alpha, if there's no beta.
Once the stable release was made, that version would supersede all of the rc,beta,alpha release versions, so none of those would be displayed (until work had begun on the next release).
Comment #5
jweowu commented#647428: Show latest prerelease (if different from recommended release) with dev releases
Comment #6
liam morlandDuplicate of #647428: Show latest prerelease (if different from recommended release) with dev releases. Thanks, jweowu.
Comment #7
liam morland