ctools 4.1.0 was released 2 days ago. At the same time focal point 4.0.* became unsupported.

Other projects will leave releases like `4.0.4` as supported (but not recommended) so it doesn't flood Admin UIs with a scary red banner asserting a module is unsupported.

This can inject stress into teams, especially from non-technical stakeholders who are security-focused and see this error banner.

Steps to reproduce

* Install update-status module and let it track your site.
* When 4.0.4 is installed, it warns about it to be unsupported and will show a status report error.

Proposed resolution

* Give people time to update. Mark 4.0.* as unsupported only when 4.1.* was out for a while, e.g. >1 month.

Note: this is a similar issue to #3446461: No time to update to supported 2.1 releases for the focal_point module.

Comments

kmonty created an issue. See original summary.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Priority: Normal » Major

Agreed on re-instating the 4.0.x releases as supported.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Active » Closed (outdated)

Thanks for raising this, and for clearly explaining the impact on dev teams and stakeholders. That concern is real.

I didn’t change the support status directly, but I’m fairly sure I caused the original issue that led to the timing here. Sorry for the confusion that created.

For what it’s worth, the update status module itself has been problematic for my team as well. We’ve ended up disabling the emails because it doesn’t handle semantic versioning particularly well, which can amplify this kind of noise. And a cron job with `composer audit` catches more transitive dependencies anyway. I wrote a script here #3553118-3: False warning about Views Bulk Operations (VBO) security update and @ressa added it here https://www.drupal.org/docs/administering-a-drupal-site/security-in-drup...

Given the age of this issue, I’m closing it as outdated to triage the queue.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.