Re: Bug tracking (was Re: +/- Inf for float8's)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Don Baccus <dhogaza(at)pacifier(dot)com>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, pgsql-hackers(at)hub(dot)org
Subject: Re: Bug tracking (was Re: +/- Inf for float8's)
Date: 2000-08-20 09:18:28
Message-ID: Pine.LNX.4.21.0008201108470.487-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> (a) a bug *tracking* system is not the same as a bug *reporting*
> system. A tracking system will be useless if it gets cluttered
> with non-bug reports, duplicate entries, etc. There must be a human
> filter controlling what gets entered into the system.

Letting any user submit bug reports directly into any such system is
certainly not going to work, we'd have "query does not use index" 5 times
a day. I consider the current *reporting* procedure pretty good; web forms
are overrated in my mind.

What I had in mind was more a databased incarnation of the TODO list. I
mean, who are we kidding, we are writing a database and maintain the list
of problems in flat text. The TODO list has already moved to the
TODO.detail extension, but we could take it a bit further.

I think currently too many issues get lost, or discussed over and over
again. Many developers maintain their own little lists. The TODO list
often cannot be deciphered by end users and hence does not get read.

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Juan Carlos Pérez Vázquez 2000-08-20 09:23:46 RE: Row Level Locking Problem
Previous Message Peter Eisentraut 2000-08-20 08:59:55 CREATE/DROP SCHEMA considered harmful