Re: Getting a bug tracker for the Postgres project

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Getting a bug tracker for the Postgres project
Date: 2011-06-03 20:36:30
Message-ID: 201106032036.p53KaUD20602@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > That doesn't mean that better integration cannot be worked on later, but
> > this illusion that a bug tracker must have magical total awareness of
> > the entire flow of information in the project from day one is an
> > illusion and has blocked this business for too long IMO.
>
> If it has only a partial view of the set of bugs being worked on, it's
> not going to meet the goals that are being claimed for it.

The problem with a bug tracker that only tracks some bugs is that people
will mistakenly believe the system is complete, when it is not.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2011-06-03 20:37:49 Re: Error in PQsetvalue
Previous Message Bruce Momjian 2011-06-03 20:35:14 Re: Getting a bug tracker for the Postgres project