[11.x] [meta] Set Drupal 11 platform and browser requirements at least six months before the release

Yay! Cleaned up the issue summary a bit. Postponing on #3118147: [meta] Set Drupal 10 platform and browser requirements six months before the release.

I opened #3215207: [11.x] [policy] Require MySQL 8.0 and MariaDB 10.6. In there, I'm proposing 10.5 for the MariaDB minimum, but leaving the item in this issue's summary at 10.4, since we haven't yet agreed on 10.5.

Created the new parent meta so as not to lose track of this (and for when we start descoping other things).

A SQLite 3.27 requirement will break the use of that DB on RHEL 8 (liable to be used by some web hosts through 2029), since it only has 3.26. Is there a particular feature in 3.27 needed that can't be easily worked around?

I believe the 3.27 in the issue summary was a typo. I opened #3346338: [11.x] [policy] Set the SQLite minimum requirement to at least 3.45 to start discussing whether to leave at 3.26 or raise to 3.34.

Adding #3266764: [11.x] [policy] Treat SQLite as a dev (rather than prod) requirement and allow it to be raised in Drupal minors as an and/or to the SQLite section since it was already a children of this issue.

Is there a particular reason to plan for the release for 2024? D10's release was driven by dependency EOLs, what is driving D11's release?

At least PHP 8.1 will loose security support at 25 Nov 2024

Thanks anypost and catch, I had completely missed #3238652, will share it widely.

Added #3357409: [11.x] [policy] Require PostgreSQL 16 for Drupal 11 for PostgreSQL.

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

I have created #3363102: [Policy] How to select the minimum required database versions.

@quietone went through and updated drupal.org webpages with the decided requirements. I opened #3421175: Update INSTALL.txt and hook_requirements() etc. with remaining Drupal 11 platform requirements to do when 11.x is ready for it. So I think we can consider this done.

Hm, there are more undecided things here, sorry about Windows support, composer and browsers.

Re composer requirements my understanding from the Symfony 7 issue is that Composer 2.2.6 and/or 2.7.0 are required to work with Symfony 7. See #3394694: [Meta] Symfony 7 compatibility.

Re browser requirements is there any reason to make it more specific than the existing rolling browser policy Drupal core has? This is the current list of supported browsers from https://www.drupal.org/docs/system-requirements/browser-requirements

• The latest release of each of the latest two supported major versions of:
  • Desktop browsers:
    • Google Chrome
    • Firefox
    • Safari
    • Microsoft Edge
    • Opera
  • Mobile browsers:
    • Safari for iOS
• The latest supported release of the latest major version of:
  • Desktop browsers:
    • Firefox ESR
    • Internet Explorer (Drupal 9 and below only)
  • Mobile browsers:
    • Chrome for Android
    • Chrome for iOS
    • UC Browser (Drupal 9 and below only)
    • Opera Mini (except for 'extreme data savings' mode)
    • Samsung Internet

Btw latest 2.7.0 release of composer is security release, so 10.2 probably should require it too!

Same time they released LTS security fix release https://github.com/composer/composer/releases/tag/2.2.23

Edit https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-...

One thing that we may want to consider & will start to get tricky is browser testing on iOS. As of iOS 17.4, iOS will begin to allow browser engines other than webkit. The requirements for this are pretty strict right now, but there's the potential for browser applications availalbe in the EU that aren't available anywhere else.

There are now other issues to discuss any changes to composer and browser.

I drafted this announcement to go out about this in light of some actual requirements planned to be committed: https://docs.google.com/document/d/1vgNvXP3zrswa2QWUbzeAod7eR1mRpj43fnvu... feedback welcome!

FWIW Composer was upgraded to ^2.7.0 in #3421371: Security update composer/composer (CVE-2023-43655).

Thanks @Damien - may as well close out the child issue given we already did it and no complaints so far.

Looks like only browser reqs left from summary #3421252: [11.x] [policy] Set Browser requirement for Drupal 11

I marked the browser support issue as fixed as I'm not sure what is left to say.

#3358248: [policy, no patch] Drop support for IIS in Drupal 11 is still outstanding and there are two possible outcomes: either very few people are using Windows, or our announcement about dropping support hasn't been seen widely enough. The upcoming blog post will re-announce the RFC in the hope that any Windows users get a chance to have their say. Otherwise, it seems likely we will drop support for Windows before Drupal 11.0.0-beta1.

Added a note about consultation time for any related RFCs to the Issue Summary so it will be copied to the similar issue for Drupal 12.

Announced requirements on Monday: https://www.drupal.org/about/core/blog/drupal-110-will-require-php-83-an... (also on various social media). Of that list, only Windows support is outstanding.

Dropping support for IIS has approval from the community, that issue is in the final steps.

Everything is complete now.