- Issue created by @kkalashnikov
- @kkalashnikov opened merge request.
- Issue was unassigned.
- Status changed to Needs work
about 2 years ago 10:56am 1 February 2023 - 🇮🇳India kkalashnikov Ghaziabad, India
To me it feels a new 3.0.x branch would keep new class/function/service to use. and support for PHP 8.1, PHP 8.2, later on.
2.0.x for ^8 || ^9
3.0.x for ^9.4 || ^10 - 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
Makes sense. Thanks for chiming in! +1 Any more thoughts?
- Status changed to Closed: outdated
about 2 years ago 9:58am 8 April 2023 - 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
After rethinking I think this merge request and issue here is rather confusing since there is no code change nor any detailed issue summary. Just a merge request by adding :3.0 I would prever to manually create a new 3.x dev branch from Drupal git repo of this project and start from there for you all to add patches for D10 compatibility in a new issue step by step to track it better as a maintainer. I will close this in favour of the one which will be created for this purpose. I also will rename this issue here to not confuse the Drupal update bot using exactly this previous title for its core compatibility issues created if desired.