Closed (fixed)
Project:
CDN
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Aug 2019 at 07:58 UTC
Updated:
25 Dec 2019 at 20:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
wim leersAs of June 3, 2019, CDN's daily test run started failing due to new deprecations. See https://www.drupal.org/pift-ci-job/1309175. Change record: https://www.drupal.org/node/3035273.
Fixed those. And yay, it means one less service to inject! 🥳
Comment #3
wim leers#2 contained mistakes.
Comment #4
wim leersAs of June 12, 2019, CDN's daily test run started gained another failure due to new deprecations. See https://www.drupal.org/pift-ci-job/1318016. Change record: https://www.drupal.org/node/3056869.
Fixed.
Comment #6
wim leersYay, down to 1 failure on 8.8! More failures on 8.7 make sense, since this patch is making the CDN module use 8.8-only APIs.
That one failure actually is also due to a change in Drupal 8.8.
As of July 30, 2019, CDN's daily test run has one actually failing test. See https://www.drupal.org/pift-ci-job/1362511. #3019393: Avoid query strings for aggregated CSS files (like JS) caused this failure:
Fixed.
Comment #7
wim leersComment #8
wim leersComment #10
wim leersThis is ready. Hopefully marking this RTBC will automatically re-test the RTBC patch against 8.8, but I'm not sure we'll be so fortunate. I think Drupal.org will use the default issue patch testing core branch, which is 8.7. We'll find out. 😊
Comment #11
wim leersI'll work on this next Friday at DrupalCon Amsterdam 🙂
Comment #12
wim leersRenaming per http://hojtsy.hu/blog/2019-oct-16/join-imadedrupal9-drupalcon-amsterdam-....
Comment #13
kristen polPer a Slack discussion with Gábor Hojtsy regarding usage of D9 tags (Drupal 9, Drupal 9 compatibility, Drupal 9 readiness, etc.), "Drupal 9 compatibility" should be used for contributed projects that need updating and "Drupal 9" was the old tag for D8 issues before the D9 branch was ready. Doing title and tag cleanup here based on that discussion.
Comment #14
wim leersDrupal 8.8.0 has been released. Let's re-run tests for #6 and land this!
Comment #15
wim leersUnfortunately, these changes can only be made if the CDN module requires Drupal 8.8.
But Drupal 8.7 is still supported.
OTOH, the CDN module has been stable for a long time now. I think it's reasonable to have release
8.x-3.3(from >6 months ago) be the last release that supported Drupal 8.6 and 8.7.People will only need to update to the next version of the CDN module if they want Drupal 9 compatibility.
Comment #16
wim leersThe test re-runs had soft failures due to new coding standards being accepted by Drupal core (see #3063323: Update drupal/coder to 8.3.6), which means the CDN module automatically inherits those too.
Comment #17
wim leersComment #18
wim leersComment #19
wim leersComment #20
wim leersComment #21
wim leersPer #15, bumping the version requirement to Drupal 8.8.
To declare Drupal 9 compatibility, we must specify the new
core_version_requirementkey incdn.info.yml. Because we're dropping support for Drupal 8.7, it's also safe to remove thecorekey. 🥳Comment #22
wim leersAlright, truly ready for Drupal 9 now!
Comment #24
wim leers