[meta] Requirements for tagging Drupal 10.0.0-beta1

For jQuery there's also #3052002: [meta] Replace JQuery with vanilla Javascript in core.

Updated the issue summary to start adding child issues in. Also un-postponing, most of this is work we can start now and have to do anyway.

Tagging so people find this issue alongside the ones being done in Drupal 9 for Drupal 10.

Segmented backend dependencies to #3197484: [META] Update / reconsider PHP dependencies for Drupal 10 like in Drupal 9.

Restore the additional links from #3197484: [META] Update / reconsider PHP dependencies for Drupal 10 since @xjm did not carry those over.

I've just added #3200913: Remove IE11 from browserlist configuration as a child issue of this one, but we may need an additional meta in-between if we collect more similar ones.

#3210486: Remove typo3/phar-stream-wrapper and associated code is a dependency removal issue we can do on the Drupal 10 branch as well. Adding.

Added CKEditor 5 introduction issue.

Updated to remove done issues. Explained Composer 2 vs 1 status better.

Added deprecated module removal and deprecated API removal META issues.

Adding #3179048: [meta] Remove dead code/unneeded compatibility layers now that PHP 8.1 is required to clean up for PHP 7 specific code.

As new major pgsql released, core should add support https://www.postgresql.org/about/news/postgresql-14-released-2318/

Update the Symfony plan (5.4 with the alpha1, 6.0 with the beta latest). Update the Twig plan given that we are going ahead with Twig 3.

Added #3266764: [11.x] [policy] Treat SQLite as a dev (rather than prod) requirement and allow it to be raised in Drupal minors to the "Shift incorrect production dependencies to dev" section. Not sure if that's exactly correct, since it's a platform requirement rather than a Composer dependency, so we can move it to a different section if we'd prefer.

Remove PHPUnit 8 compatibility layers

Is this done, or are there issues remaining for that?

Adding #3283358: [META] Make Drupal 9/10 compatible with PHP 8.2 to issue summary.

I've taken a pass at moving done tickets to a 'done' section, so that the remaining blockers list only has blockers. Can probably improve some formatting now we have a shorter list too but one thing at a time.

I've also moved #3258987: Status report should warn about OPcache bug in PHP 8.1.0 to 8.1.5 and #3067261: [Plan] Remove jQuery UI components used by Drupal core and replace with a set of supported solutions to should haves since the release blocking parts are done.

PHPUnit 10 is also a should-have unless they do a release, in which case it'll be a must-have, so leaving as a must-have for now - better to downgrade if we hit beta before they release, and we might be able to commit forward compatibility issues before an official release too.

Opened #3284420: Remove Composer 1 specific code paths from Drupal 10 which was of the "issue needed".

Opened #3284422: [META] Symfony 6.2 compatibility as well. Not sure whether there will be or need to be Drupal 9.5 changes thanks to that, so titled and targeted Drupal 10 for now.

I've moved #3179048: [meta] Remove dead code/unneeded compatibility layers now that PHP 8.1 is required to 'should have' because it should mostly be dead code removal that can happen in minor releases. If something is not simply dead code removal we might want to promote it to a beta blocker individually.

Also moving psr/log 3 to done.

Add link to the Meta for removing Color

Adding #3281559: Remove modernizr usages from core which was in one of the sub-issues but not listed explicitly yet. Modernizr deprecation itself has been moved to 10.x

I reorganized the first few categories in the must-have list a bit. These changes make it easier for me to grasp the list, so I hope it's helpful for others. If not, we can revert to the prior issue summary.

As part of #74, I added #3109556: Update from Yarn 1 to Yarn 4 as a must-have to the issue summary. It was already a child issue of this one, and I'm guessing that it's a must-have, but if that's incorrect, we can move it to the should-have list or remove it entirely.

Adding #3278415: Remove usages of the JavaScript ES6 build step, the build step itself, and associated dev dependencies to the issue summary. Even though it's a child of #3238497: What to do with assets build step?, I think that as we're getting closer to the beta date, it's helpful to start explicitly calling out some of the key child issues here. We probably don't want to overdo that (e.g., I don't think we need to list each of the remaining CKE5 issues individually here), so it'll be a case by case judgment call as to which child issues benefit from being listed here vs. adding noise.

There are seven open issues and no closed issues in the jQuery 3.7.0 milestone, and 35 open issues in the jQuery 4.0.0 milestone, so I think we can safely say that there won't be a jQuery 4 release in any shape or form before the beta deadline at this point and that jQuery 3 has at least a release or two left in it before focus shifts, moving to the 'should have' list which will probably need migrating to a new issue at some point.

PHPUnit 10 on the other hand is 90% complete (although it was 90% complete two months ago too according to #3217904-58: [meta] Support PHPUnit 10 in Drupal 11, that's a familiar feeling) so I don't think we should move it anywhere just in case.

Swapped the modernizr issue to #3269082: Remove HTML5 details collapse polyfill since that's the actual usage we need to remove and it's just one issue.

#3290810: Remove updates added prior to 9.4.0 (9.4.4 for ckeditor) and add 9.4.0 database dumps is done.

#3223443: [policy, no patch] Process for dealing with EOL PHP versions during the Drupal 10 and future release cycles is listed as a blocker, but I think all the blocking parts are in, and we're left with fairly theoretical questions about how to react to dependency updates that might drop PHP 8.1 support, so IMO this should move to should haves.

Also seems like all the actionable parts of #2659890: [Policy] [Plan] Drupal 9 and 10 markup and CSS backwards compatibility (marking starterkit stable, deprecating stable) are currently listed independently as 'should haves' and we could move it to a should haves (or out of scope) too.

Not doing that just yet though in case I've missed something.

#3238497: What to do with assets build step? is another policy-ish issue that seems like it's basically been decided in #3238497: What to do with assets build step? and might be possible to just mark fixed at this point, but it needs multiple committer sign-offs.

Opened #3304303: Drupal 10.0.0 requirements to migrate various should haves and/or new blockers over to when we're ready to close this issue.

Also moved #3223443: [policy, no patch] Process for dealing with EOL PHP versions during the Drupal 10 and future release cycles to a should have since the release blocking parts of that are done, and we're mostly trying to plan ahead for later 10.x minor releases in there now.

Move completed items to Done

Add issue to deprecate farbtastic to IS.

All link to issues tagged 'Drupal 10 beta should-have'

Moving 'additional dependency removals' to 'should have' since so far all the deprecated modules are removed in Drupal 10, and we've been making an effort to commit deprecations/removals very close to each other.

#3307241: Deprecate Classy in favor of the new Starterkit Theme kept under the radar, but is also a theme deprecation/removal one.

We have a nearly green patch on #3284422: [META] Symfony 6.2 compatibility. Apart from a serious upstream regression we found that is now fixed (thanks Nikolas Grecas for fixing it), there is nothing too worrying in there. So while we need to split some changes out and do the actual update once Symfony 6.2 is available and keep checking against HEAD until it gets to release candidate, I think it's 'done' as far as the beta deadline goes.

• Added Classy to should-have list per #98.
• PHP 8.2 RC has been released, so updated that item accordingly.
• +1 to #99, but I did not move that, since I don't know if that still needs more discussion.

EasyRDF is gone, two of the farbtastic issues are done and the status report page issue is done. Moved them there.

Removed the "Update dependencies: (None to update at the moment)" item from the issue summary, since given that there are none at the moment, it's a duplicate of the "Update all dependencies ... immediately before tagging 10.0.0-beta1" item.

Add Stable. move Classy to done.

Quickedit is done. Updates IS

Stable is also done.

IS lists #3283358: [META] Make Drupal 9/10 compatible with PHP 8.2 as must-have, but it is tagged as should-have, which is right?

Re #114 it should be moved to "should-have" as remaining issues does not break API and could be fixed in other betas as bug/task

Moved php 8.2 to shouldhaves in is

I wonder though, have the changes in childissues of that issue been tagged with release notes if they need them. Seems like it was quite a few small incremental issues.

Yes PHP 8.2 we've managed to land the issues that definitely required deprecations, what's left shouldn't be disruptive.

Also moving Symfony 6.2 to should have, since we've got about as far as we can on #3284422: [META] Symfony 6.2 compatibility without having an actual release to update to there as well.

Probably still need to organise things a bit into release candidate blockers (which the above two would be), beta-eligible, and anything that might need to move to 10.1 (Stable 9, forum etc.). #3304303: Drupal 10.0.0 requirements is the meta.

Moved #3284422: [META] Symfony 6.2 compatibility and #3283358: [META] Make Drupal 9/10 compatible with PHP 8.2 to 3304303 as per @catch in the Drupal 10 meeting and also above. He also indicated some should haves may move there, but I don't think that is my call to make.

Going through the should-haves:

Modernizr: this is actually done as far as 10.0.0 is concerned, we're going to deprecate the library in 10.1 for removal in 11.0 in #3239980: Deprecate Modernizr.

Module removals: this is done, anything left over is 10.1 now.

EOL PHP versions - copied over already.

Remove PHP < 8.1 compatibility layers - moved over since most of those should be fine for beta clean-up tasks.

Starterkit: done.

Dependency updates - copied over since we'll need to do that all over again during beta.

core_version_requirement + incorrect deprecations are 10.1 tasks now since those will involve new deprecations.

#12 I think we are de-facto leaving that as is.

#13 is 10.1 now.

Adding triage credits and moving to fixed!