Must-haves prior to tagging 11.0.0-beta1
Release notes: #3425287: 11.0.0-beta1 release notes
- Fully support PHP versions above the Drupal 11 minimum.
- Update or decouple/remove PHP (Composer) dependencies.
- Symfony:
- ✅ Update to Symfony 7: #3394694: [Meta] Symfony 7 compatibility
- Support and recommend Symfony 7.1: #3447191: Support and recommend Symfony 7.1.0-BETA1 for Drupal 11.0.0-beta1
- PHPUnit:
- Doctrine
- Re-evaluate other backend dependencies in the year prior to the release.
- Symfony:
- Update or decouple/remove frontend dependencies.
- Remove all deprecated code, libraries, and BC layers.
- ✅ Update deprecation message in DeprecatedServicePropertyTrait: #3318342: DeprecatedServicePropertyTrait should point to 11.0
- Resolve critical 10.x -> 10.x upgrade path bugs.
- #3416928: [Meta] Remove updates added up until 10.3.0 from Drupal 11 Remove old upgrade paths up to 10.x.0 and add new database dumps.
- Resolve any significant outstanding bugs for new platform requirements (PHP, Composer, etc.)
- Resolve any 11.0.x-only security or data integrity issues.
- Resolve other D11-only upgrade blockers.
- Update all dependencies (backend and frontend) to their latest versions immediately before tagging 11.0.0-beta1.
- Update COPYRIGHT.txt #3413657: Update COPYRIGHT.txt for 2024
Should-haves prior to tagging 11.0.0-beta1
These become beta targets if they are not completed by the deadline, and may contribute to other adjustments to the schedule (TBD).
- Fix DB fixtures process:
- jQuery UI
- Ensure that 10.x.x-beta1 ships with logic for warnings about future security coverage EOLs (both for the LTS version of Drupal itself, and for PHP versions, with dates hard coded as needed).
- Backbone: #3145958: [META] Re-evaluate use of Backbone.js in core (marked internal in Drupal 10)
- Disruptive issues:
- Other issues TBD.
Comments
Comment #2
gábor hojtsyFix two typos.
Comment #3
xjmComment #4
xjmComment #5
xjmComment #6
xjmComment #7
xjmComment #8
xjmComment #9
xjmComment #10
xjmComment #11
quietone commentedComment #12
quietone commentedAdd an item to update DeprecatedServicePropertyTrait to point to 12.0
Comment #13
catchAdding doctrine/annotations -> attributes. We can always descope if we don't want to make it a blocker, but best guess is it'll need to be.
Comment #14
catchComment #15
longwaveComment #16
longwaveComment #17
xjmComment #18
lauriiiWhy is #1899236: Add new Splitbutton render element to eventually replace Dropbutton listed as a must have for Drupal 11?
Comment #19
catchI think that might be my fault, was trying to list the remaining tasks to get rid of jQuery UI, but dropbutton doesn't rely on jQuery UI, so it's not one of them.
Comment #20
danielvezaAdded #3352548: Leftover D10 deprecations in the contextual module & #3352549: Remove deprecations in ajax.js to the IS
Comment #21
gábor hojtsyUpdating title, tags and version number based on recent announcement at https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-...
Comment #22
quietone commentedComment #23
quietone commentedComment #24
quietone commentedComment #25
quietone commentedComment #26
quietone commentedRemoved two items from the IS where the parent has changed.
Comment #27
quietone commentedComment #28
xjmComment #29
xjmComment #30
quietone commentedAdding #3409456: Remove SDC deprecated code before 11.0.0
Comment #31
catchOpened #3411839: [11.x] Update to jQuery 4.0.x beta.
Comment #32
quietone commentedComment #33
longwaveComment #34
catchMoving the jQuery UI dialog and autocomplete to 'should haves' - they don't block jQuery 4 (as far as I can tell), so our main issue is jQuery theoretically dropping support for them before the EOL of Drupal 11.
Comment #35
quietone commentedComment #36
quietone commentedComment #37
andypost✅ Yarn 4
Comment #38
catchUpdating the Doctrine item to point to the active issue since there's still a lot to do there. I think we probably want all of core's annotations converted to attributes prior to 11.0.0, but things like deprecating attribute discovery overall I'm less sure about - some of that could be in Drupal 11.1 for removal in 12 maybe.
Comment #39
quietone commentedComment #40
catchComment #41
catchMoved jQuery form to should-haves because we've completely forked it to an internal library with jQuery 4 compatibility.
Moved Backbone to should have - we have less backbone usage in Drupal 11 (only contextual links and toolbar), so it makes sense to target backbone decoupling there, rather than having to deal with tour in Drupal 10, at least we should concentrate on those first.
Added in the jQuery 4 dialog incompatibility issue directly here for more visibility.
Comment #42
catchI'm not sure what to do about #3378393: Hardcode security coverage EOL dates for Drupal 10.last-1 and 10.last and #3361728: Make 10.x EOL warning better than the 9.5.x one, I think we might want to introduce those warnings to 10.5, moving them to 'should have' for now because I am pretty sure the longer support timeline for 10.x makes them not 'must haves' for 11.0.0 any more, but not sure at all beyond that.
Comment #43
wim leers#41: Contextual links has a tiny amount of JS and could easily be updated to not rely on Backbone anymore.
AFAIK the community is working on a total overhaul of the Toolbar, which would remove that reliance on Backbone AFAICT, but … that seems unlikely to make the
10.3.xdeadline?Comment #44
quietone commentedComment #45
quietone commentedComment #46
quietone commentedComment #47
quietone commentedThe removal of deprecated extensions is complete.
Comment #48
xjmComment #49
xjmAdding #3444792: Prepare for PHPUnit 10 to the IS explicitly since it was reported that we broke GitLab CI templates.
Comment #50
xjmThe next step before we close this issue is to create the D12 issue tree with anything we're descoping from D11 to D12, as well as another child issue from the parent meta for beta targets.
Comment #51
xjmI created #3449808: [12.x] [meta] Requirements for tagging 12.0.0-beta1 to start.
We also need a second followup for beta targets for this version (like the void typehints one as well as a few scattered missed deprecations, updating to stable versions of Symfony and jQuery UI, etc.).
Comment #52
xjmAdded that as well: #3449815: [meta] Requirements for tagging 11.0.0-rc1
The next step is to correctly sort the above should-haves from this issue into whether they should be 11.x beta targets or 12.x beta requirements or should haves.
Comment #53
xjmI moved #3378393: Hardcode security coverage EOL dates for Drupal 10.last-1 and 10.last to beta2.
Comment #54
jcnventuraI'd say whatever may remain, the objective of this issue has been achieved: https://www.drupal.org/project/drupal/releases/11.0.0-beta1
Comment #55
jcnventuraOK. Read #52 and #53 now, and maybe there's still work to do, even if the objective has been achieved.
Comment #56
damienmckennaGiven that 11.0.0-rc1 was released already, should the sub-issues be listed in another plan issue and this one closed?
Comment #57
longwaveYup this can be closed as fixed now, the rc1 issue is already closed. I tried to credit everyone who contributed to keeping the issue summary up to date.
The Drupal 12 top level meta is also open: #3449806: [12.x] [meta] Release Drupal 12 in 2026 so removing the followup tag for that.
Comment #59
quietone commented