Re: Commit fest queue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Tom Dunstan <pgsql(at)tomd(dot)cc>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commit fest queue
Date: 2008-04-10 16:07:43
Message-ID: 2679.1207843663@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Or :)

> I can open a web browser, go to tracker.postgresql.org,
> review the list of open patches, click one, download, review, comment,
> upload new patch if required, done.

And then no one sees your revised patch (except someone watching the
tracker like a hawk). This is not the way to have a discussion,
which is fundamentally what our process is.

As I said before, I am uninterested in any proposals for a fundamental
change in our processes. I want an index page that makes sure that
nothing that's supposed to get done in a commit fest gets forgotten.
I do not need what you propose, and I wouldn't voluntarily use it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-04-10 16:09:14 Re: Commit fest queue
Previous Message Bruce Momjian 2008-04-10 16:02:29 Re: Commit fest queue