Re: Commitfest Update - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Commitfest Update
Date
Msg-id CA+TgmoZSBNhX0zCkG5T5KiQize9Aq4+ec+uqLcfBhm_+12MbQA@mail.gmail.com
Whole thread Raw
In response to Re: Commitfest Update  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Commitfest Update  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Mar 31, 2022 at 10:11 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This reminds me of a point I've been meaning to bring up: it seems to
> often happen that someone adds their name as reviewer, but then loses
> interest and doesn't do anything more with the patch.  I think that's
> problematic because people see that the patch already has a reviewer
> and look for something else to do.  Would it be feasible or reasonable
> to drop reviewers if they've not commented in the thread in X amount
> of time?

In theory, this might cause someone who made a valuable contribution
to the discussion to not get credited in the commit message. But it
probably wouldn't in practice, because I at least always construct the
list of reviewers from the thread, not the CF app, since that tends to
be wildly inaccurate in both directions. So maybe it's fine? Not sure.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Unit tests for SLRU
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Accept IP addresses in server certificate SANs