| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hans Buschmann <buschmann(at)nidsa(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 19:49:41 |
| Message-ID: | 665818.1634154581@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-10-13 19:57:33 | Re: prevent immature WAL streaming |
| Previous Message | Peter Geoghegan | 2021-10-13 19:23:23 | Re: Next Steps with Hash Indexes |