[meta] Requirements for tagging Drupal 11.0.0-beta1

Why is ✨ Add new Splitbutton render element to eventually replace Dropbutton Needs work listed as a must have for Drupal 11?

I 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.

Added 🐛 Leftover D10 deprecations in the contextual module Fixed & 🐛 Leftover D10 deprecations in ajax.js Needs work to the IS

Updating title, tags and version number based on recent announcement at https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-... →

Removed two items from the IS where the parent has changed.

Adding 📌 Remove SDC deprecated twig functions before 11.0.0 Postponed

Opened 📌 Update to jQuery 4.0.x beta Active .

Moving 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.

✅ Yarn 4

Updating 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.

Moved 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.

I'm not sure what to do about 📌 Hardcode security coverage EOL dates for Drupal 10.last-1 and 10.last Postponed and 📌 Make 10.x EOL warnings better than the 9.5.x one Postponed , 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.

#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.x deadline?

The removal of deprecated extensions is complete.

Adding #3444792: Prepare for PHPUnit 10 → to the IS explicitly since it was reported that we broke GitLab CI templates.

The 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.

I created 🌱 [12.x] [meta] Requirements for tagging Drupal 12.0.0-beta1 Active 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.).

Added that as well: 📌 [meta] Requirements for tagging 11.0.0-beta2 Active

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.

I moved 📌 Hardcode security coverage EOL dates for Drupal 10.last-1 and 10.last Postponed to beta2.

I'd say whatever may remain, the objective of this issue has been achieved: https://www.drupal.org/project/drupal/releases/11.0.0-beta1 →

OK. Read #52 and #53 now, and maybe there's still work to do, even if the objective has been achieved.