On 10/10/05, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> Old-timers will recall that we already had one bad experience with an
> early open-source bug tracker, which has left people a bit shy of the
> concept too. I think a large part of that had to do with confusion
> between the purposes of bug *reporting* and bug *tracking*. A mailing
> list does very well for reporting issues that might be bugs, but not so
> well for tracking the status of acknowledged bugs.
This "tracking" feature is crucial for us. We're working towards a
large scale deployment of PostgreSQL across our enterprise, but not
having an easy way to get the status of all reported bugs against our
particular version isn't very comforting. Having a bug tracker in
place would make life much easier, and my advocacy job much less
trying.
I sincerely hope the team will consider using one...bugtraq is fine,
so is trac...just as long as one is in place.
Thanks,
JB
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
