| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Greg Smith <greg(at)2ndquadrant(dot)com>, Jay Levitt <jay(dot)levitt(at)gmail(dot)com>, Alex <ash(at)commandprompt(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug tracker tool we need |
| Date: | 2012-04-19 14:25:59 |
| Message-ID: | 1334845458-sup-6826@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tom Lane's message of mié abr 18 03:12:09 -0300 2012:
>
> Magnus Hagander <magnus(at)hagander(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2012-04-19 14:32:33 | Re: Bug tracker tool we need |
| Previous Message | Sandro Santilli | 2012-04-19 13:45:12 | Re: Gsoc2012 idea, tablesample |