Surely this should be the recommended release and should be green just like the D6 version. This should be a simple fix.

Comments

ezra-g’s picture

ezra-g commented
Status: Active » Postponed

The 3.0 release is not green because it contains 2 modules that have new versions. They are incorrectly listed by Drupal.org as security updates (they are not) and therefore the release gets listed as "not recommended".

This will be resolved with the 3.1 release.

mgifford’s picture

mgifford
he/him
Primary language English
commented

Thanks!

BTW, to get a faster response time I think you'd need to be sitting beside me and watch me hit Save on my initial image. Amazing! :)

devin carlson’s picture

devin carlson commented
Category: task » support
Status: Postponed » Closed (works as designed)

From #2 it sounds like this is fixed.

Distributions will be red if one or more of the modules that they utilize has a newer version available which has been marked as a security release. See #1962678: Commons 3.2 release is incorrectly marked as red by the Drupal.org packager.

ezra-g’s picture

ezra-g commented
Category: support » task
Status: Closed (works as designed) » Postponed

I believe the proper status for this is "Postponed."

Per #1:

They are incorrectly listed by Drupal.org as security updates (they are not) and therefore the release gets listed as "not recommended".

If you follow the references in #1962678: Commons 3.2 release is incorrectly marked as red by the Drupal.org packager, you'll end up at #1954840: Packaging is incorrect in saying there's insecure module in distribution, which is the underlying issue here.

Feel free to change the status back with an explanation if you disagree.

lsolesen’s picture

lsolesen commented
Issue summary: View changes
Status: Postponed » Fixed

It is green now.

Status: Fixed » Closed (fixed)

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