public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Andres Freund <[email protected]>
Cc: [email protected]
Cc: Peter Geoghegan <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: Amit Kapila <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Subject: Re: When to drop src/tools/msvc support
Date: Sat, 08 Apr 2023 15:30:20 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Andres Freund <[email protected]> writes:
> Do we want to drop src/tools/msvc support in 16 (i.e. now), or do it early in
> 17?
On the one hand, it feels like something we shouldn't do after
feature freeze. On the other hand, continuing to maintain three
build systems is a real drag (although you could argue that there
shouldn't be much churn there until the tree opens for 17).
We clearly can't consider it in any case until the buildfarm
is prepared, with all the Windows animals updated to a compatible
client script. I don't know what timeline Andrew has in mind
for that.
I guess I'd vote for pulling the trigger in v16 if we can get that
done by the end of April. Once we're close to beta I think it
must wait for v17 to open.
regards, tom lane
view thread (21+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: When to drop src/tools/msvc support
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox