| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Ford <david(at)blue-labs(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Vince Vielhaber <vev(at)michvhf(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Link to bug webpage |
| Date: | 2001-08-24 03:40:40 |
| Message-ID: | 3B85CCB8.B926C711@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Ford wrote:
>
> Tom Lane wrote:
>
> >Peter remarked that he wouldn't use a bug database unless it has some
> >input filtering to remove all the non-bug issues that currently clutter
> >the pgsql-bug archives.
So the first thing to decide is the purpose of the bug database, do we
want
to have
a) a marketing tool to show that we are bugfree and all bugs are fixed
fast
(at lest this is what started this thread :)
or
b) a convenient place to look up all open issues - here bugzilla would
be graet.
We have been using bugzilla with good results for our own projects
(mainly
Amphora http://www.amphora.ee/eng/ - a quite large groupware product
based on
Zope, PostgreSQL and other freeware technologies).
So if it does suit both a smaller-than-PGSQL group of
programmers/testers/users
like us and a huge group like mozilla it should also suit a medium-sized
group
like postgreSQL.
-----------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2001-08-24 03:47:51 | Re: Re: List response time... |
| Previous Message | Tom Lane | 2001-08-24 03:12:26 | Re: A couple items on TODO |