From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-hackers@postgresql.org, Peter Geoghegan <pg@bowt.ie>,
        Andrew Dunstan <andrew@dunslane.net>,
        "Jonathan S. Katz" <jkatz@postgresql.org>,
        Amit Kapila <amit.kapila16@gmail.com>,
        Alvaro Herrera <alvherre@alvh.no-ip.org>
Subject: Re: When to drop src/tools/msvc support
In-reply-to: <20230408191007.7lysd42euafwl74f@awork3.anarazel.de>
References: <20230408191007.7lysd42euafwl74f@awork3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Sat, 08 Apr 2023 12:10:07 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3611415.1680982220.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 08 Apr 2023 15:30:20 -0400
Message-ID: <3611416.1680982220@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3611416.1680982220%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Do we want to drop src/tools/msvc support in 16 (i.e. now), or do it ear=
ly 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