Horton

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

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, Hans Buschmann <buschmann@nidsa.net>
Cc: Michael Paquier <michael@paquier.xyz>, Laurenz Albe <laurenz.albe@cybertec.at>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-10-13T20:11:12Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add support for Visual Studio 2022 in build scripts

On 10/13/21 3:49 PM, Tom Lane wrote:
> Hans Buschmann <buschmann@nidsa.net> writes:
>> In the long of this process Microsoft announced the general availability of VS200 for Monday, November 8, see
>> https://devblogs.microsoft.com/visualstudio/join-us-november-8th-for-the-launch-of-visual-studio-2022/
>> 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.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com