Re: unresolved bugs

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: unresolved bugs
Date: 2010-01-07 06:40:54
Message-ID: 1262846454.14688.15.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On ons, 2010-01-06 at 16:44 -0800, Josh Berkus wrote:
> > Personally, I was more hoping we could consider fixing some of them...
>
> Agreed. I really don't think a bug tracker helps us. We need two things:
>
> (1) to respond to bug submissions immediately and fix them, and
> (2) if we can't fix the bugs immediately, to add them to a TODO list
>
> Adding stuff to a bug tracker is just a way to procrastinate on it
> indefinitely.

The problem is that your two-step plan requires failsafe human
intervention, whereas a bug tracker doesn't.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2010-01-07 07:37:15 Re: Status of plperl inter-sp calling
Previous Message Fujii Masao 2010-01-07 06:19:29 Re: 'replication' keyword on .pgpass (Streaming Replication)