The first nightly test run for the recommendations after publicly releasing AM:A failed the Drupal 10-installability job.
That job tries to install all the vetted recommendations on Drupal 10. It passes tests as long as the % that is installable, is low enough, the script does this:
echo "\n🟢 Drupal 10 compatibility coverage on (vetted recommendations): " . round($compatibility_coverage, 2) . "%";
echo "\n🟢 Drupal 10 compatibility module count on (vetted recommendations): " . $compatible_module_count . "/" . $total_module_count;
if ($compatibility_coverage > 90) {
exit(1);
}
It looks like literally in the 12 hours since making the announcement, one more module was made Drupal 10-compatible 😅
It reached 90.96%, versus <90% 24 hours earlier!
At least one more very important module is missing: https://www.drupal.org/project/bean_migrate → . Possibly several. So I think it's time to reassess this "90% threshold".
A more pragmatic approach might be to require 100% but allow this CI job to fail. That way, until it's green, switching to Drupal 10 (a huge effort!!) would result in net fewer sites being able to migrate to "modern Drupal".
Fixed
1.8
Recommendations
Issue #3390759: Require 100%, not 90% of modules to be Drupal 10-...
Automatically closed - issue fixed for 2 weeks with no activity.