Re: On status data and summaries

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: On status data and summaries
Date: 2006-10-12 21:26:02
Message-ID: 200610122126.k9CLQ2d05159@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Sullivan wrote:
> On Thu, Oct 12, 2006 at 01:56:37PM -0500, Jim C. Nasby wrote:
> > *ahem* nudge people to update the status of what they're working on once
> > a month.
>
> Well, though, remember that the point of this was supposed to be to
> make things easier for the developers, who are already spending (it
> would seem) too many cycles keeping on top of this. Or maybe I just
> misunderstood what the problem was people were having.

No, my point was that right now I only do it during feature freeze, so
we know what has to happen to get to beta (and that seems to work well).
What I think people wanted was something like that, but maintained
during the development cycle, so they would know what features our being
worked on, and by whom.

One great thing about the list I maintain is that it is a flat text
file, so I can update it in seconds.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-10-12 21:28:48 Re: Hints proposal
Previous Message Greg Stark 2006-10-12 21:23:46 Re: Hints WAS: Index Tuning Features