Re: CommitFest #3 and upcoming schedule - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: CommitFest #3 and upcoming schedule
Date
Msg-id 50C51514.9000206@fuzzy.cz
Whole thread Raw
In response to Re: CommitFest #3 and upcoming schedule  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On 9.12.2012 22:41, Jeff Janes wrote:
> On Sun, Dec 9, 2012 at 10:47 AM, Tomas Vondra <tv@fuzzy.cz> wrote:
>>
>> IMHO many of the patches that are currently marked as "needs review" and
>> have no reviewers, were actually reviewed or are being discussed
>> thoroughly on the list, but this information was not propagated to the
>> CF page.
> 
> Should active discussion on the hackers list prevent someone from
> doing a review?  I know I am reluctant to review a patch when it seems
> it is still being actively redesigned/debated by others.
>
> Maybe a new status of "needs design consensus" would be useful.

IMHO introducing new statuses won't improve the state. Moreover reaching
a design consensus is a natural part of the review process.

I see those discussions as a part of the review process, so it's not
that an active discussion means 'no review' (although the CF page states
"needs review" or "no reviewer" for such patches).

There's nothing wrong with doing yet another review for a patch, but in
most cases I tend to agree with the points already raised in the
discussion so it's not really productive. Thus I share the same
reluctance to do more reviews for those actively discussed patches.

My point is that some of the "idle patches" are actually quite active in
the background, no one just updated the CF page. And I see many such
patches moved forward over the last few days.

Tomas



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Proof of concept: auto updatable views [Review of Patch]
Next
From: Tom Lane
Date:
Subject: Re: Proof of concept: auto updatable views [Review of Patch]