Re: [RRR] Reviewfest 2010-06 Plans and Call for Reviewers - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [RRR] Reviewfest 2010-06 Plans and Call for Reviewers
Date
Msg-id 4C35BA250200002500033252@gw.wicourts.gov
Whole thread Raw
In response to Re: [RRR] Reviewfest 2010-06 Plans and Call for Reviewers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [RRR] Reviewfest 2010-06 Plans and Call for Reviewers  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> wrote:

> Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
>>> or had major design issues
>>
>> That's a much harder problem.  The set of people who can review
>> for that is rather smaller than the set who can see if a patch
>> applies without error.
>
> Well, true.  But reporting whether the patch applies without error
> is about the most minimal review possible

I didn't mean to imply that only the two extremes of review ("does
the patch apply?" and "does this patch have a major overall design
flaw?") were the only things to try to address now; I was just
responding to your observation that these comprised a lot of the
activity of the first CommitFest last year, and that the latter is
harder to address without a review by a senior developer.  I suspect
that one person could check for bitrot in all pending patches with a
one or two FTE day's effort, and if that's done within the next few
days, it might allow time for fixes before the start of the CF free
up more of the first week of the CF to more substantive review.

Nice comments later in the email, though; I hope you won't mind if
you find excerpts popping up in the code review Wiki pages.  ;-)

-Kevin

pgsql-hackers by date:

Previous
From: Pavel
Date:
Subject: Re: GSoC - code of implementation of materialized views
Next
From: Robert Haas
Date:
Subject: Re: [RRR] Reviewfest 2010-06 Plans and Call for Reviewers