Re: list of acknowledgments for PG15

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:48:36
Message-ID: Y0RpBGBMEO3/A3PK@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 10, 2022 at 02:44:22PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Mon, Oct 10, 2022 at 02:41:06AM -0400, Tom Lane wrote:
> >> 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.
>
> > Is the issue that we are really only crediting people whose commits/work
> > appears in major releases, and not in minor ones?
>
> What Peter has said about this is that he lists everyone whose name
> has appeared in commit messages over thus-and-such a time frame.
> So it doesn't matter which branch is involved, just when the contribution
> was made. That process is fine with me; I'm just seeking a bit more
> clarity as to what the time frames are.

Oh, that's an interesting approach but it might mean that, for example,
PG 16 patch authors appear in the PG 15 major release notes. It seems
that the stable major release branch date should be the cut-off, so no
one is missed.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Indecision is a decision. Inaction is an action. Mark Batterson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2022-10-10 18:48:49 Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Previous Message Tom Lane 2022-10-10 18:44:22 Re: list of acknowledgments for PG15