Project pages should allow showing alpha, beta, release candidates along with full releases. For example, in the Drupal reset module, the stable release is 7.x-1.0. I have also just published drupal_reset 7.x-1.1-rc1. I ought to be able to get that to display on the yellow background. That would lead to more such releases being tested before they become stable, which would improve the quality of stable releases.

Comments

dddave’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

Closing old issues that went stale or never got support.

liam morland’s picture

Can 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.

dddave’s picture

Try 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.

jweowu’s picture

This 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).

liam morland’s picture

Status: Closed (won't fix) » Closed (duplicate)
liam morland’s picture