From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Commitfest status |
Date: | 2008-03-07 18:11:49 |
Message-ID: | 200803071811.m27IBnD06560@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Aidan Van Dyk wrote:
> > > Only 150 "patches" in that queue, if you eliminate all the discussions
> > > and threads:
> > > http://people.ifax.com/~aidan/pg/patches.mbox
> >
> > True, but we can't just discard all the ideas we had --- we need to
> > decide if they are worth persuing or adding to TODO.
>
> Sure, but ideas *are* discussed on the list as they come up. But it's
> not ideas that get committed during the commitfest.
>
> It's up to the "itchy" person to use the discussion on the lists around
> the ideas to come up with something concrete that *needs* to be more
> than hand-waving to be reviewed during a commit fest.
>
> That concrete something could be:
> *) A complete "patch"
> *) A partial patch (implementing step X of the discussed goals
> *) A defined implementation proposal (a patch minus C-language code)
>
> Ideas and discussion are important (actually vital). But the
> commit-fest is a period that reviewers and committers set apart time to
> process the *products* of ideas and proposals that have come about so
> far.
Well, when do we make decisions on these non-patch issue? Seems the
commit fest is the right time to that too.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-07 18:12:31 | Re: Commitfest status |
Previous Message | Alvaro Herrera | 2008-03-07 18:11:10 | Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconn return status > > |