From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | James Keener <jim(at)jimkeener(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Bug Tracker |
Date: | 2016-01-11 20:07:18 |
Message-ID: | 1553.1452542838@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> On 01/11/2016 11:18 AM, James Keener wrote:
>> Are there any technical reasons that the project doesn't use a bug
>> tracker (beyond pgsql-bugs)?
> on -hackers there is on an ongoing thread about this [1] but the long
> and short is a: It is a culture issue. Warning, the thread has been
> going on for almost 4 months.
4 months? More like fifteen years. We actually *had* a bug tracker,
for a short while long ago, and it was an unmitigated failure (search
for "Keystone" in the archives, from mid-1999). The reason the longtime
hackers are suspicious of such proposals is it's not clear how to avoid
that fate the next time around. Anything we do has to adapt itself to
existing community habits, a lot more than vice versa, or it will go
down the tubes as well.
My own postmortem on that attempt is here:
http://www.postgresql.org/message-id/9072.966741720@sss.pgh.pa.us
and the surrounding thread is well worth reading as well. Doesn't
really seem like the discussion has moved much since 2000 :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Regina Obe | 2016-01-11 20:07:20 | Re: Code of Conduct: Is it time? |
Previous Message | Regina Obe | 2016-01-11 20:04:18 |