- Issue created by @tr
- 🇺🇸United States tr Cascadia
I removed the D8 testing configurations in DrupalCI. They haven't been running for a year, because DrupalCI shut down support for Drupal 8.
- 🇮🇳India rinku jacob 13 Kerala
Hi @TR, I have reviewed your patch. The patch was successfully applied and removed D8 testing configurations in DrupalCI. Adding screenshots for the references . Need RTBC+1
- 🇵🇹Portugal jcnventura
@TR it's your module and of course you do what you feel most comfortable with. That being said, this issue makes little sense on it's own. There are no changes here that would require the change to core_version_requirement, so it does feel somewhat extraneous.
This would make lot of sense in the commit that uses the new D9/D10 APIs that forces this change.
- 🇺🇸United States tr Cascadia
That's all true, but the other side is that there are now half a dozen issues that all require dropping D8 support, and rather than bundling this removal of D8 support into something totally unrelated and having it conflict with the other half dozen patches that need to do the same thing. Even simple coding standards things like null coalesce can't be done in D8.
I think it's cleaner to have a clear commit the marks the boundary between what should work in D8 and what will not. This is a major version jump, not like the other issues which just require a higher minor point release.
Those other issues also have different requirements for the lowest version of D9 they support, and I want to make sure that the requirements continue to match the code base. So most issues WILL be changing that lowest version of D9 as we make the necessary changes for D10,
- Status changed to Fixed
about 2 years ago 7:18pm 6 February 2023 Automatically closed - issue fixed for 2 weeks with no activity.