Re: Commit fest queue - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Commit fest queue
Date
Msg-id 7688.1207805076@sss.pgh.pa.us
Whole thread Raw
In response to Re: Commit fest queue  ("Brendan Jurd" <direvus@gmail.com>)
Responses Re: Commit fest queue  ("Brendan Jurd" <direvus@gmail.com>)
Re: Commit fest queue  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Commit fest queue  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
"Brendan Jurd" <direvus@gmail.com> writes:
> Personally I don't feel that using a patch tracker or wiki is any more
> onerous than using an email list, and it's a whole lot more responsive

There are a couple of differences in my mind.  One is that the email
list provides an automatic historical archive, whereas trackers tend to
be all about current state.  Another is that the email list provides a
"push" mechanism for putting the proposed patch under the noses of a
bunch of people, a few of whom will hopefully take a sniff ;-).
A tracker is very much more of a "pull" scenario where someone has to
actively go looking for pending/proposed changes.

Obviously there are virtues on both sides of this, which is why I think
we need both mechanisms.  The simplest way to integrate them AFAICS
is to use the tracker as an index on the email traffic.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Free Space Map data structure
Next
From: Heikki Linnakangas
Date:
Subject: Re: Index AM change proposals, redux