Re: Bug tracker tool we need - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Bug tracker tool we need
Date
Msg-id 1334845458-sup-6826@alvh.no-ip.org
Whole thread Raw
In response to Re: Bug tracker tool we need  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Excerpts from Tom Lane's message of mié abr 18 03:12:09 -0300 2012:
>
> Magnus Hagander <magnus@hagander.net> writes:
> > I think this cleraly outlines that we need to remember that there are
> > *two* different patterns that people are trying tosolve with the
> > bugtracker.
>
> Yeah, remember we drifted to this topic from discussion of management of
> CF patches, which might be yet a third use-case.  It's not obvious that
> it's the same as tracking unfixed bugs, at least; though maybe the
> requirements end up the same.
>
> > Any tool we'd go for should aim to cover *both* usecases.
>
> Not convinced that we should expect one tool to be good at both
> (or all three) things.

So maybe we need more than one tool to present the information to
different kinds of users, but we need only *one* database backing them
all, right?

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Sandro Santilli
Date:
Subject: Re: Gsoc2012 idea, tablesample
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Bug tracker tool we need