Problem/Motivation
Drupal 10 and Drupal 11 have different versions of phpunit.
In Drupal 11 with PhpUnit 11, we can use attributes. In PhpUnit 10 we cannot.
In the end this module will run on a Drupal 11 or 12 website.
It made sense for a while to test with Drupal 10, just to see if some old stuff was working in 10 but not 11, given that the module was initially ported to an even earlier core version (8 or 9).
But now we can drop it I think.
localize also upgraded to Drupal 11 in https://gitlab.com/drupal-infrastructure/sites/localize/-/commit/992fcb7....
Steps to reproduce
Proposed resolution
Stop all CI checks with Drupal 10.
UPDATE: Actually just fully drop Drupal 10 support.
(that means update the *.info.yml files, because our composer.json says nothing about drupal core)
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork l10n_server-3564210
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
donquixote commentedLet's just go all the way and remove older Drupal versions from *.info.yml files.
I am not sure where else we have to change anything.
At least we now know that we can refactor everything with Drupal 11 in mind, or even 11.3.
Comment #4
donquixote commentedComment #5
donquixote commentedIf people still want to test with Drupal 10 locally, they can just revert the commit.
Comment #6
donquixote commentedActually... localize project is still on Drupal 10!
Do we care?
EDIT: No it is not :)
Comment #7
donquixote commentedComment #8
donquixote commentedIt is blocking the CI now for other issues..
Comment #9
pierregermain commentedThe changes look good and accomplish the goal of dropping Drupal 10 support and unblocks the CI.
Comment #13
fmb commented