Re: Commitfest Update - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Commitfest Update
Date
Msg-id 7c6bf719-ff27-33f3-7dae-cc5c93ce4e6a@timescale.com
Whole thread Raw
In response to Re: Commitfest Update  (Pavel Borisov <pashkin.elfe@gmail.com>)
Responses Re: Commitfest Update
List pgsql-hackers
On 7/17/22 08:17, Nathan Bossart wrote:
> On Fri, Jul 15, 2022 at 09:37:14PM -0500, Justin Pryzby wrote:
>> I'm not suggesting to give the community regulars special treatment, but you
>> could reasonably assume that when they added themselves and then "didn't remove
>> themself", it was on purpose and not by omission.  I think most of those people
>> would be surprised to learn that they're no longer considered to be reviewing
>> the patch.
> 
> Yeah, I happened to look in my commitfest update folder this morning and
> was surprised to learn that I was no longer reviewing 3612.  I spent a good
> amount of time getting that patch into a state where I felt it was
> ready-for-committer, and I intended to follow up on any further
> developments in the thread.  It's not uncommon for me to use the filter
> functionality in the app to keep track of patches I'm reviewing.

I'm sorry again for interrupting that flow. Thank you for speaking up
and establishing the use case.

> Of course, there are probably patches where I could be removed from the
> reviewers field.  I can try to stay on top of that better.  If you think I
> shouldn't be marked as a reviewer and that it's hindering further review
> for a patch, feel free to message me publicly or privately about it.

Sure. I don't plan on removing anyone else from a Reviewer list this
commitfest, but if I do come across a reason I'll make sure to ask first. :)

--Jacob



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Commitfest Update
Next
From: Andrew Dunstan
Date:
Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size