- Issue created by @longwave
- Status changed to Needs review
over 1 year ago 1:44pm 31 March 2023 - π³πΏNew Zealand quietone
Adding a parent. I will note over there that this is still in discussion.
- Status changed to Needs work
over 1 year ago 3:26am 1 April 2023 - π¬π§United Kingdom catch
Per π Use PHP attributes instead of doctrine annotations Fixed we won't remove annotations support in Drupal 11, although we should be able to fully deprecate it, so we should go ahead here.
- First commit to issue fork.
- Assigned to spokje
- Issue was unassigned.
- Status changed to Needs review
10 months ago 11:57am 5 February 2024 - Status changed to RTBC
10 months ago 8:14pm 5 February 2024 - πΊπΈUnited States smustgrave
Searched for AnnotationRegistry::registerLoader and 3 instances were replaced. Doesn't seem to have caused any failures
- π¬π§United Kingdom longwave UK
Marking this as 11.x only, as we prefer not to bump major versions of dependencies in a minor release, and if we did we should try to add compatibility for both versions at once - not impossible but let's save the effort if we can.
- ππΊHungary GΓ‘bor Hojtsy Hungary
This is listed under "add a compatibility layer to Drupal 10" in π± [meta] Add compatibility for the latest major and minor versions of dependencies to Drupal 10 Active , do you think that is not needed @longwave? If so, that should be moved to reference from the updates to be done in the 11.x branch and not from the "prepare Drupal 10" issue.
- π³π±Netherlands spokje
Not much to shim IMHO.
AnnotationRegistry::registerLoader
is removed, but that seems only been used in/vendor
of contrib:
https://git.drupalcode.org/search?group_id=2&scope=blobs&search=%22Annot...Same for
AnnotationRegistry::registerAutoloadNamespace
:
https://git.drupalcode.org/search?group_id=2&scope=blobs&search=%22Annot... - π¬π§United Kingdom longwave UK
Yeah I don't think any compatibility layer is needed, if anyone was using doctrine/annotations directly (which seems fairly unlikely) they may have to make minor changes as part of the D10-11 cycle, but the APIs that we provide on top are unchanged.
- π³π±Netherlands spokje
So are we OK with moving this issue from π± [meta] Add compatibility for the latest major and minor versions of dependencies to Drupal 10 Active to π± [11.x] [meta] Requirements for tagging 11.0.0-alpha1 Active ?
- π¬π§United Kingdom longwave UK
The parent of this issue is already π± [meta] Requirements for tagging Drupal 11.0.0-beta1 Active , I updated π± [meta] Add compatibility for the latest major and minor versions of dependencies to Drupal 10 Active to remove
doctrine/annotations
. - π³π±Netherlands spokje
Thanks, the latter is what I tried to ask, but failed miserably at (too many METAs!!! ;)
- Status changed to Needs work
9 months ago 5:01pm 23 February 2024 The Needs Review Queue Bot β tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide β to find step-by-step guides for working with issues.
- Status changed to Needs review
9 months ago 6:02pm 23 February 2024 - π³π±Netherlands spokje
11.x is open for 11.0.x changes AFAIK, so this is at least NR, maybe even RTBC, since I only did a rebase since the last RTBC.
- Status changed to RTBC
9 months ago 6:32pm 23 February 2024 - πΊπΈUnited States smustgrave
Rebase seems good, so going to put back in RTBC.
- Status changed to Fixed
9 months ago 4:50pm 29 February 2024 Automatically closed - issue fixed for 2 weeks with no activity.