From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Joshua Tolley <eggyknap(at)gmail(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: bugs that have not been replied-to on list |
Date: | 2010-04-10 11:30:35 |
Message-ID: | 4BC0615B.20908@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 캔SQL : Postg토토 캔SQL 메일 링리스트 : 2010-04-10 11:30 이후의 PGSQL-BUGS |
Craig Ringer wrote:
> Dave Page wrote:
>
>> This basically indicates that we need an issue tracker. There, look -
>> now see what you made me do :-(
>
> Please?!?
>
> I wonder, if EDB just went ahead and set one up, would people start
> using it? I've been tempted to do it myself, but I'm not confident I can
> handle the bandwidth/hosting for a decent tracker with upload capability
> etc.
>
> Or just use Launchpad. It's actually pretty good, and very accessible,
> plus many people already have logins.
>
> I know people are worried it'll just become full of many ignored,
> dupliate or useless reports, but that's what -bugs is anyway; it's just
> less visibly so. Dups and non-bugs are easily closed by the same folks
> who're active on -bugs triaging here.
the problem is not setting one up (in fact we had multiple serious
attempts at that) but more of how it should interact with the lists,
what tool we should use and "do we even want one". There are tons of
discussions on that very topic in the archives (and also in the wiki).
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2010-04-11 09:29:55 | Re: bugs that have not been replied-to on list |
Previous Message | Craig Ringer | 2010-04-10 11:16:27 | Re: bugs that have not been replied-to on list |