Neil Conway <neilc@samurai.com> writes:
> Beyond "the core developers want to stick to email", I think there is a
> good reason that we should stick primarily to email for project
> management: Bugzilla and similar systems are "point to point", whereas a
> mailing list is multicast[1].
That seems to me to be a great summary of the issue. I've been dealing
with Bugzilla for a few years now in my employment with Red Hat, and
I think the bottom line for that kind of system is that it's designed
to limit the visibility of issues, rather than expose them.
Now that is just exactly what you want for a corporate-sized bug
tracking system --- at Red Hat, I do not want to hear about bugs in the
kernel, or X, or a thousand other components that I have no expertise in
--- but I cannot see that restricting the flow of information is what we
need for Postgres.
I think most of the real advantages of bug trackers that have been
mentioned in this thread have to do with history and searchability.
We have the raw info for that, in the pgsql-bugs and pgsql-commmitters
mail archives, and so it seems to me that this reduces to the perennial
gripe that we don't have good enough search tools for the archives.
regards, tom lane
