From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: On status data and summaries |
Date: | 2006-10-12 14:18:21 |
Message-ID: | 200610121418.k9CEILL07843@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> On Thu, Oct 12, 2006 at 07:14:36AM -0400, Andrew Sullivan wrote:
> > On Wed, Oct 11, 2006 at 06:26:50PM -0400, Bruce Momjian wrote:
> > >
> > > Funny, sounds like what I usually do. I welcome the assistance.
> >
> > Well, yes, that was my impression too. The complaint in the thread
> > that started all this, as I understood it, was that there were big,
> > hairy features that tended to have long discussions about them, and
> > very few people among even the committers seemed to have a clear idea
> > of exactly where things stood at the end of coding.
>
> Something else that would be helpful is summarizing discussions that
> don't result in code (perhaps on the developer wiki). That way if
> someone wants to see the history of something they don't have to wade
> through the list archives just to have some idea of what's being talked
> about. This is probably especially important when the discussion results
> in some design ideas/proposals but never moves forward from there.
What I started to do for this is to add the thread URL to the TODO item
it relates to.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-10-12 14:20:43 | Re: On status data and summaries |
Previous Message | Martijn van Oosterhout | 2006-10-12 14:08:55 | Re: Hints WAS: Index Tuning Features |