Closed (works as designed)
Project:
Drupal.org site moderators
Component:
Broken link
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Mar 2012 at 23:02 UTC
Updated:
18 Nov 2013 at 21:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
webernet commentedIt's a beta, not a final release. It was likely never green.
Comment #2
TomDude48 commentedModules will give you a green status if they are in beta. Are installation profiles handled differently?
Comment #3
randallknutson commentedHow do we go about changing to a green (recommended) status? We've set all the release information so it should be recommended but it still shows up in yellow.
I'm including screenshots of the settings and the download section.
Is there another setting somewhere to make it recommended, is this a bug somewhere or is there a new policy for installation profiles that says beta cannot be recommended?
Comment #4
randallknutson commentedI'm pretty sure this is not as designed. If so, how do we set it to green?
Comment #6
patrickd commentedRelease settings are correct - if there's not a special rule for profiles - here's definitely something wrong.
If you have a look at the release list with firebug and you disable the yellow color - it's getting green! :o
Seems like a CSS bug?
Comment #7
patrickd commentedOkay - now I got the solution.
It has the css flag warning what is making the release yellow colored.
The reason for the "warning" is that there are outdated modules in the package.
Just have a look at the release information: https://drupal.org/node/1469170
Comment #8
kreynen commentedThis was before the D7 upgrade. Additional changes to how this should work are being discussing in #2137095: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how?