Welling, Bexley, London
Account created on 3 December 2009, almost 15 years ago
#

Recent comments

🇬🇧United Kingdom GreenReaper Welling, Bexley, London

It depends on whether we expect people to [be able to] upgrade to the latest available distro, or whether we want to work with all distros that are still supported during part of the release period.

My experience is that sometimes you have a server and have to use it without potentially breaking other stuff by updating to a new version of a distro - especially if it's not your server to start with. But I'm not someone who installs lots of sites, and I imagine when you do that the process is to install a new OS too, perhaps by plonking it into a container. (It's also viable to install multiple versions of PostgreSQL on Drupal-derived distros, which isn't quite so easy for e.g. SQLite. But for RHEL/,CentOS 7 and similar distributions this only works up to PostgreSQL 15.)

There's no doubt that PostgreSQL 16 has many improvements but few of them seem to relate to programming features - is the use of syntax such as JSON_ARRAY(), JSON_ARRAYAGG(), and IS JSON beneficial enough to say "you can't install without PG 16"? I didn't hear people speaking up when I asked about features.

As I said before, PG 16 matches the Drupal support lifetime better. I'm using it now on Drupal Bookworm using PostgreSQL's APT repo. I just want us to be clear that the cost is that in some cases Drupal 11 won't be usable with PostgreSQL on a still-supported system without being able to upgrade the OS or add a new repo and binaries for PG 16.

🇬🇧United Kingdom GreenReaper Welling, Bexley, London

With the two year release cadence 🌱 [policy] Decide how long major Drupal versions should be supported Needs review PG 15 makes sense:

Honestly PostgreSQL 16 would be a better match in terms of upstream timelines but obviously not for most distributions, and it is not clear that the changes are that significant from a development perspective. PostgreSQL 15 at least added MERGE and wider ICU collation support. Perhaps those coding the DB layer could chime in on features that might be important.

🇬🇧United Kingdom GreenReaper Welling, Bexley, London

I tried

composer require 'drupal/aristotle:^3.0.3'

It got further, removing the drupal/core line. The issue is it requires css_editor which has not made a release with Drupal 10 support.

Production build 0.71.5 2024