| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Mikael Kjellström <mikael(dot)kjellstrom(at)gmail(dot)com> |
| Subject: | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
| Date: | 2024-08-07 23:59:17 |
| Message-ID: | 534C7906-80AA-4356-8D64-88E9A8106B33@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Aug 7, 2024, at 22:49, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> I think it's highly likely that we will see complaints for any support we
> deprecate. OpenSSL 1.0.2 will however still be supported for another 5 years
> with v17 (which is ~9years past its EOL date) so I don't feel too bad about it.
I’ve cut 1.0.1 at least by myself last year, and definitely not regret it while not hearing complains on the matter. 1.0.2 being a LTS matters more in the likeliness to see complaints, but I think it’s time to just let it go. So let’s do it and move on.
I’d seriously consider 1.1.0 as well for this release cycle as something to drop but I’m ok to keep it as the code gains are not really here. The 1.0.2 cut removes a lot of code and concepts particularly with the libcrypto threading and its locks!
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2024-08-08 00:35:05 | Re: Unused expression indexes |
| Previous Message | Alena Rybakina | 2024-08-07 23:53:35 | Re: POC, WIP: OR-clause support for indexes |