Feedback-ID: ia2694551:Fastmail
Date: Tue, 11 Apr 2023 19:44:20 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>,
	Magnus Hagander <magnus@hagander.net>,
	Robert Haas <robertmhaas@gmail.com>, 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>
Subject: Re: When to drop src/tools/msvc support
Message-ID: <20230411174420.lq6wp7vzuqmnu3dg@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ZDShWe5w9cLkHh2Y@paquier.xyz>
Archived-At: <https://www.postgresql.org/message-id/20230411174420.lq6wp7vzuqmnu3dg%40alvherre.pgsql>
Precedence: bulk

On 2023-Apr-11, Michael Paquier wrote:

> Getting a CI job able to do some validation for MSVC would be indeed
> nice.  What's the plan in the buildfarm with this coverage?  Would all
> the animals switch to meson (Chocolatey + StrawberryPerl, I assume)
> for the job or will there still be some coverage with MSVC for v16
> there?

If we keep MSVC support in 16, then I agree we should have a CI task for
it -- and IMO we should make ti automatically triggers whenever any
Makefile or meson.build is modified.  Hopefully we won't touch them
much now that the branch is feature-frozen, but it could still happen.

Do we have code for it already, even if incomplete?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/