Must-haves prior to tagging 12.0.0-beta1

Release notes: #3564240: 12.0.0-beta1 release notes

All issues tagged "12.0.0 beta blocker".

  1. ✅ Fully support PHP versions above the Drupal 11 minimum.
  2. Update core façade and core packages for new requirements.
  3. Update or decouple/remove PHP (Composer) dependencies.
  4. Update or decouple/remove frontend dependencies.
  5. Remove all deprecated code, libraries, and BC layers.
  6. Resolve critical 11.x -> 11.x upgrade path bugs.
  7. Prevent downgrades between equivalent minor versions:
  8. Remove old upgrade paths up to 12.x.0 and add new database dumps.
  9. Resolve any significant outstanding bugs for new platform requirements (PHP, Composer, etc.)
  10. Resolve any 12.0.x-only security or data integrity issues.
  11. Resolve other 12.0.x-only upgrade blockers.
  12. Update all dependencies (backend and frontend) to their latest versions immediately before tagging 11.0.0-beta1.
    • Composer dependencies
    • Yarn dependencies
  13. Update COPYRIGHT.txt
  14. 12.0.0-beta1 release notes. #3564240: 12.0.0-beta1 release notes

Should-haves prior to tagging 12.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).

  1. Dynamically prevent equivalent updates based on known equivalent minors? See #20.
  2. Fix DB fixtures process:
  3. jQuery UI
  4. Ensure that 12.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).
  5. Backbone: #3145958: [META] Re-evaluate use of Backbone.js in core (marked internal in Drupal 10)
  6. Drupal CMS :
  7. Disruptive issues:
  8. Other issues

Comments

xjm created an issue. See original summary.

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes
mstrelan’s picture

Issue summary: View changes

Added #3418267: Support PHPUnit 11 in Drupal 11 to the issue summary. I guess it should become a child issue of this? Not sure as it already has a parent.

quietone’s picture

Issue summary: View changes
mondrake’s picture

Issue summary: View changes

By the time of this, PHPUnit will likely be on its version 13, and close to 14 - if they keep the cycle of 1 major per year.

quietone’s picture

quietone’s picture

Issue summary: View changes
andypost’s picture

There's a chance to stop using masterminds/html5 dependency adopting native PHP 8.4 parser

So could have #3463613: Explore PHP 8.4 native HTML 5 parser vs html5-php

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes

Add an Drupal 11 should have I found.

quietone’s picture

Title: [12.x] [meta] Requirements for tagging Drupal 12.0.0-beta1 » [12.x] [meta] Requirements for tagging 12.0.0-beta1
longwave’s picture

longwave’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes

This morning @longwave and I discussed the possibility of simplifying the equivalent updates situation a bit now that our release cycle is more predictable. Currently, we have to remember each minor to backport an issue preventing downgrades from 10.6.1 to 11.3.0 or 11.2.x (etc.). As of 12.0.0-beta1, we will know whether 12.0 is equivalent to 11.4 or 11.5, and which version is equivalent to 12.1, etc. So we might be able to dynamically prevent equivalent updates that way.

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

gábor hojtsy’s picture

Issue summary: View changes

Adding PHPUnit 12 issue and Symfony 8 issue.

gábor hojtsy’s picture

Issue summary: View changes

PHP 8.5 support is done and we don't expect more PHP minor versions to come out before Drupal 12, so marking as done :)

gábor hojtsy’s picture

Issue summary: View changes

Update Symfony related items.

damienmckenna’s picture

Should the tag link point to 12.0.0 beta blocker, which shows results, instead of "12.0.0 beta1 blocker" which doesn't exist?

quietone’s picture

Issue summary: View changes

Yes

damienmckenna’s picture

Two more quick questions:

  • Should this issue have the beta blockers tag?
  • Should issues that block issues with the tag also have the tag? For example #3561671 blocks #3527936 but only 936 has the tag, 671 doesn't.
quietone’s picture

Not sure this should have the beta blocker tag as it is about managing the things to do, so maybe 12.0.0 release priority is better? But if your searching by tag for 'beta' then it would be helpful for this to show up. So let's try that approach.

gábor hojtsy’s picture

Issue summary: View changes
longwave’s picture

gábor hojtsy’s picture

Issue summary: View changes

PHPUnit 13 was postponed, also elaborating on Symfony being done already.

mondrake’s picture

longwave’s picture

Issue summary: View changes

Adding #3555916: Update to htmx 4 per discussion with @fathershawn and @Carson Gross in Slack.

longwave’s picture

Issue summary: View changes

Fixing link

catch’s picture

Issue summary: View changes

Removed #3189416: [PP-1] Remove jQuery Form dependency from misc/ajax.js because the entire AJAX system is getting replaced in #3404409: [Plan] Gradually replace Drupal's AJAX system with HTMX. Better to expend the effort there.

#3145958: [META] Re-evaluate use of Backbone.js in core is more or less done apart from toolbar module removal, but we'll want to actually remove the library from core too, so probably the right place to have it in should haves.

longwave’s picture

Issue summary: View changes

Added two disruptive issues to the should-have list.