From: Michael Paquier <michael@paquier.xyz>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Remove support for Visual Studio 2013
Date: Mon, 16 May 2022 19:34:31 +0900
Message-ID: <YoIot8WgNe2fFZjn@paquier.xyz> (raw)
In-Reply-To: <CA+hUKG+ZNWbdqL0UX1M=Py8zxQ-xLwinRfgwO4EK-K4c-rkAnQ@mail.gmail.com>
References: <YoH2IMtxcS3ncWn+@paquier.xyz>
<CA+hUKG+ZNWbdqL0UX1M=Py8zxQ-xLwinRfgwO4EK-K4c-rkAnQ@mail.gmail.com>
On Mon, May 16, 2022 at 08:46:31PM +1200, Thomas Munro wrote:
> Looking at the published lifecycle info, 2017 is the oldest still in
> 'mainstream' support[4], so it wouldn't be too crazy to drop VS 2015
> too, just like those other projects. That said, it sounds like there
> is no practical benefit to being more aggressive than you are
> suggesting currently (as in, we wouldn't get to delete any more crufty
> untestable dead code by dropping 2015, right?), so maybe that'd be
> enough for now.
FWIW, one of my environments is using VS2015, because I have set it up
years ago and I am lazy to do this setup except if I really have to :)
The code works as far as I know, still I am not really excited about
cutting support for more versions than necessary, particularly as this
does not simplify the C code more.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: michael@paquier.xyz, thomas.munro@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Remove support for Visual Studio 2013
In-Reply-To: <YoIot8WgNe2fFZjn@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox