Problem/Motivation

Something in the process of doing SAs is resulting in previous non-stable releases of a project not being marked as insecure when a stable release is marked a security fix.

Proposed resolution

Mark Beta, alpha and RC releases as insecure when a later stable release is marked a security release.

User interface changes

Beta, alpha, RC releases will show as insecure when a later stable release is marked a security release.

API changes

TBD

Data model changes

TBD

Comments

DamienMcKenna created an issue. See original summary.

drumm’s picture

drumm
he/him
Location NY, US
commented
Project: Drupal Security Team » Drupal.org customizations
Version: 7.x-1.x-dev » 7.x-3.x-dev

We can’t completely switch, since affected versions does not cover Drupal-7-compatible contrib.

What we can do for core and modern contrib is replace the “Mark previous releases as insecure” checkboxes with “Releases that will be marked as insecure: …” text.