From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: list of acknowledgments for PG15 |
Date: | 2022-10-10 18:30:35 |
Message-ID: | Y0Rky/NgkSJlSHcT@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Oct 10, 2022 at 02:41:06AM -0400, Tom Lane wrote:
> I don't wish to object to adding Nakamori-san here, but I feel like we
> need a policy that doesn't require last-minute updates to release notes.
>
> As far as I've understood, the idea is to credit people based on the
> time frame in which their patches were committed, not on the branch(es)
> that the patches were committed to. Otherwise we'd have to retroactively
> add people to back-branch acknowledgements, and we have not been doing
> that. So a patch that goes in during the v16 development cycle means
> that the author should get acknowledged in the v16 release notes,
> even if it got back-patched to older branches. What remains is to
> define when is the cutoff point between "acknowledge in v15" versus
> "acknowledge in v16". I don't have a strong opinion about that,
> but I'd like it to be more than 24 hours before the 15.0 wrap.
> Could we make the cutoff be, say, beta1?
Is the issue that we are really only crediting people whose commits/work
appears in major releases, and not in minor ones?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-10-10 18:44:22 | Re: list of acknowledgments for PG15 |
Previous Message | Bruce Momjian | 2022-10-10 18:20:37 | Re: subtransaction performance |