From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 14:17:28 |
Message-ID: | Pine.BSF.4.21.0008201116140.3758-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 20 Aug 2000, Peter Eisentraut wrote:
> 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.
A TODO list that one can add comments to ...
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-08-20 14:20:16 | Re: Flex vs Lex |
Previous Message | Tiago Antão | 2000-08-20 13:56:16 | A GNU-Prolog/PostgreSQL interface |