Re: list of acknowledgments for PG15 - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: list of acknowledgments for PG15
Date
Msg-id Y0Rky/NgkSJlSHcT@momjian.us
Whole thread Raw
In response to Re: list of acknowledgments for PG15  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: list of acknowledgments for PG15  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

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




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: subtransaction performance
Next
From: Tom Lane
Date:
Subject: Re: list of acknowledgments for PG15