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 <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
