| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Commit fest queue |
| Date: | 2008-04-10 05:24:36 |
| Message-ID: | 7688.1207805076@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Brendan Jurd" <direvus(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-04-10 05:38:05 | Re: Index AM change proposals, redux |
| Previous Message | Heikki Linnakangas | 2008-04-10 05:18:40 | Re: Free Space Map data structure |