Re: PG 18 relnotes and RC1 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 18 relnotes and RC1
Date
Msg-id 163638.1756650883@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG 18 relnotes and RC1  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: PG 18 relnotes and RC1
Re: PG 18 relnotes and RC1
List pgsql-hackers
Peter Eisentraut <peter@eisentraut.org> writes:
> On 30.08.25 18:52, Tom Lane wrote:
>> I suppose that the expectation is that every release note item
>> will be credited to someone.  Why does this item lack a credit?

> Maybe I'm understanding this differently, but the "Migration" section 
> ought to be advice about the migration, which is not a place to 
> communicate credit.  In the case I added, the item is the result of some 
> changes that are already listed and credited elsewhere in the "Changes" 
> section.

One answer could be to remove the commit-details comment block from
that item, thereby making the added URL go away too.  However, that
will look a bit odd when the neighboring items all have credits and
URLs.

I think our past practice has been to list any one item either in
Migration or the following sections, not in both places.  This item
seems to adhere to that too: I don't see that commit hash anywhere
else.  So I'm not clear why you're finding this duplicative?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Mankirat Singh
Date:
Subject: Re: ABI Compliance Checker GSoC Project
Next
From: Tom Lane
Date:
Subject: Re: ecpg test thread/alloc hangs on sidewinder running NetBSD 9.3