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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
