Re: minimum Meson version

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: minimum Meson version
Date: 2025-06-18 18:36:43
Message-ID: 1156880.1750271803@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> In the context of RHEL, it says here [1] that RHEL8 maintenance
> support runs through May 2029 while extended support runs through
> May 2031. That would still mean we're supporting RHEL8 for another
> four years. I'm not sure what the corresponding dates are for
> other LTS vendors.

I checked Debian and SUSE and noted that their "extended support"
windows are a lot shorter than RHEL's, just two or three years.
So maybe we shouldn't buy into RHEL's five-year window. I do take
Jelte's point that it's unlikely somebody wants to run a bleeding-edge
PG release on a platform that's many years out from end of full
support; if they are using such a platform they probably prize
stability above all else.

Maybe we could compromise on

If the expected PG major version release date is more than N years
after the end of full support for an LTS distribution, that OS
version does not need to be supported.

Defining it relative to "full support" also reduces questions about
whether extended support means the same thing to every LTS vendor.

If we set N=2 then we could drop RHEL8 support in PG 19; if we
set N=3 then it'd be PG 20 (measuring from end of full support
in May 2024). I'd be okay with either outcome.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2025-06-18 18:48:16 Re: Fixes inconsistent behavior in vacuum when it processes multiple relations
Previous Message David G. Johnston 2025-06-18 18:36:04 Re: Document NULL