Re: AW: VS2022: Support Visual Studio 2022 on Windows

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hans Buschmann <buschmann(at)nidsa(dot)net>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: VS2022: Support Visual Studio 2022 on Windows
Date: 2021-10-13 20:11:12
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 10/13/21 3:49 PM, Tom Lane wrote:
> Hans Buschmann <buschmann(at)nidsa(dot)net> writes:
>> In the long of this process Microsoft announced the general availability of VS200 for Monday, November 8, see
>> This date is just some hours after the wrapup for our minor release on November 11.
> Ugh, bad timing.
>> Barring any objections I suggest to apply the patch just before this weekend in November to have the support for Microsofts Developer Suite for the following 3 months available.
> Immediately before a release is the worst possible time to be applying
> non-critical patches. I think better options are to
> (1) commit now, using the RC release's version as the minimum, or
> (2) wait till just after our release cycle.
> Of course, if we only plan to commit to HEAD and not back-patch,
> this is all moot.

No, we always try to backpatch these so that we can have buildfarm
animals that build all live branches.

I really don't see that we need to be in a hurry with this. There is no
requirement that we support VS2022 on day one of its release. Three
months really won't matter. Impatience doesn't serve us well here.



Andrew Dunstan

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-10-13 20:36:55 Re: prevent immature WAL streaming
Previous Message Andrew Dunstan 2021-10-13 20:06:32 Re: [RFC] building postgres with meson