| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| 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 18:56:37 |
| Message-ID: | 20061012185637.GP28647@nasby.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-10-12 19:00:12 | Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers |
| Previous Message | Neil Conway | 2006-10-12 18:50:52 | Re: Documentation fix for --with-ldap |