- Issue created by @drumm
Before we migrate the project_release_supported_versions
table to modern Drupal, it would be best to reduce the complexity on D7 first, with
📌
Remove “recommended” status for releases?
Active
The 8.x
version of the update status XML API has recommended_major
. 2.4% of requests from modern versions of Drupal still use the 8.x
API endpoint instead of current
.
Only Drupal 8.x, up to 8.8.2 uses the 8.x
API. It looks like this version of Drupal does use recommended_major
when the they are not running a supported version. So we should keep recommended_major
.
We can either:
recommended_major
to the highest supported version, which would be straightforward recommended_major
to the highest supported version with a stable release, which might be more correctTo keep the logic simple, and since the stakes are a bit low with the low usage, we can set it to the highest supported version. There might not be that many supported versions compatible with Drupal 8.x anyway.
recommended_major
will change for some projects.
Active
3.0
Code