Re: Add version macro to libpq-fe.h - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Add version macro to libpq-fe.h
Date
Msg-id 701d660a-0306-cd13-3f62-dc71aeb45c76@dunslane.net
Whole thread Raw
In response to Re: Add version macro to libpq-fe.h  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 6/21/21 12:34 PM, Tom Lane wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:
>> On 21 Jun 2021, at 17:27, Robert Haas <robertmhaas@gmail.com> wrote:
>>> What will prevent us from forgetting to do something about this again,
>>> a year from now?
>> An entry in a release checklist could perhaps be an idea?
> Yeah, I was wondering if adding an entry to RELEASE_CHANGES would be
> helpful.  Again, I'm not sure that this coding rule is much more
> likely to be violated than any other.  On the other hand, the fact
> that it's not critical until we approach release does suggest that
> maybe it'd be useful to treat it as a checklist item.
>
>         


Maybe for release note preparation, since that's focused on new
features, but this doesn't sound like a release prep function to me.


cheers


andrew


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




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: disfavoring unparameterized nested loops
Next
From: Simon Riggs
Date:
Subject: Re: Discarding DISCARD ALL