Re: PG 18 relnotes and RC1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 18 relnotes and RC1
Date: 2025-08-31 14:34:43
Message-ID: 163638.1756650883@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(at)eisentraut(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-31 14:52:49 Re: ecpg test thread/alloc hangs on sidewinder running NetBSD 9.3
Previous Message Mankirat Singh 2025-08-31 14:17:41 Re: ABI Compliance Checker GSoC Project