| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | 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>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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-18 06:12:09 |
| Message-ID: | 22369.1334729529@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wolfgang Wilhelm | 2012-04-18 06:23:53 | Re: Bug tracker tool we need |
| Previous Message | Magnus Hagander | 2012-04-18 05:55:36 | Re: Bug tracker tool we need |