From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: When to drop src/tools/msvc support |
Date: | 2023-04-10 23:53:15 |
Message-ID: | d889d599-e2f1-fcfc-6fc4-74f3d517104d@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/10/23 4:50 PM, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Thus, +1 on actually keeping it up and dropping it immediately as v17
>> opens, giving them a year of advantage. And probably updating the docs
>> (if anybody were to read them.. but at least then we tried) stating
>> that it's deprecated and will be removed in v17.
>
> Yeah, I think that's the only feasible answer at this point.
> Maybe a month or two back we could have done differently,
> but there's not a lot of runway now.
>
> Once we do drop src/tools/msvc from HEAD, we should make a point
> of reminding -packagers about it, in hopes that they'll work on
> the transition sooner than next May.
[personal opinion, not RMT]
The last point would be my reasoning for "why not now" given deadlines
are a pretty good motivator to get things done.
That said, if the plan is to do this "shortly thereafter" for v17 and it
makes the transition easier, I'm all for that.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2023-04-11 00:16:12 | Re: Should vacuum process config file reload more often |
Previous Message | Michael Paquier | 2023-04-10 23:52:57 | Re: When to drop src/tools/msvc support |