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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Hans Buschmann <buschmann@nidsa.net>

Cc: Michael Paquier <michael@paquier.xyz>, Andrew Dunstan <andrew@dunslane.net>, Laurenz Albe <laurenz.albe@cybertec.at>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2021-10-13T19:49:41Z

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 →

Add support for Visual Studio 2022 in build scripts
- 82881a9b9d0f 10.20 landed
- 1061e41ff9ae 11.15 landed
- 420d5e40b3a3 12.10 landed
- baef657d3c84 13.6 landed
- 0e681fa45875 14.2 landed
- b2265d305d81 15.0 landed

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.

			regards, tom lane