Re: Please claim review items for commit fest!

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Dave Page" <dpage(at)pgadmin(dot)org>
Cc: "Marko Kreen" <markokr(at)gmail(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Please claim review items for commit fest!
Date: 2008-07-02 12:39:02
Message-ID: 8763roqx3t.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Dave Page" <dpage(at)pgadmin(dot)org> writes:

> On Wed, Jul 2, 2008 at 11:44 AM, Marko Kreen <markokr(at)gmail(dot)com> wrote:
>
>> The comments should go to wiki? Not mailing list?
>
> It's a fine line (and slightly bendy line) - but simple comments can
> go on the wiki, discussion should go to the list and be referenced
> from the wiki.
>
> For example, see the 'returned for feedback' section at the end of the
> last commit fest: http://wiki.postgresql.org/wiki/CommitFest:2008-05

It is a fine line, but I think anything about the substance of the patch
really ought to go to the list so other people get a chance to respond.

IMHO the wiki is best thought of as a kind of group "todo list". Notes about
the status of a patch and a bottom-line summary for future reference makes
sense to keep there. Something like "review found problems with memory
management" so we can reprioritize it without rereading the emails for every
item.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Roberts, Jon 2008-07-02 12:48:56 Re: pg crashing
Previous Message Peter Eisentraut 2008-07-02 12:18:28 Re: GIT repo broken