Re: On status data and summaries - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: On status data and summaries
Date
Msg-id 20061012185637.GP28647@nasby.net
Whole thread Raw
In response to Re: On status data and summaries  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: On status data and summaries
List pgsql-hackers
On Thu, Oct 12, 2006 at 01:53:27PM -0400, Andrew Sullivan wrote:
> On Thu, Oct 12, 2006 at 10:20:43AM -0400, Bruce Momjian wrote:
> > use a wiki to track open development items, with some status, like I did
> > for the open items list for 8.2.  I usually only do that during feature
> > freeze, but could expand it and open it up for others to edit.
> 
> So do I understand this as a suggestion to pick some threads, keep
> track of them, but otherwise shut up until feature freeze?  That's
> ok with me, if that's what helps; but I was under the impression from
> the meta-discussion last time that people didn't think that was
> working.  Anyone?

If the ball gets dropped on something we want to know well before
feature-freeze.

Something that might be useful would be to send out a monthly status
report of all active development. That'd be pretty easy to do if there
was a wiki with all the info available.. the trick would just be to
*ahem* nudge people to update the status of what they're working on once
a month.
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers
Next
From: "Jim C. Nasby"
Date:
Subject: Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers