Don Baccus wrote:
>
> >(Side note: Folks, we need a real bug/issue-tracking system. We just
> >discussed this a month ago ("How PostgreSQL's floating point hurts
> >everyone everywhere"). If anyone's interested in porting Bugzilla or some
> >other such system to PostgreSQL and putting it into use, let me know.)
istm that it is *not* that easy. We tried (very briefly) a bug tracking
system. Whatever technical problems it had (which other tools may not),
the fundamental problem is that the mailing lists do a *great* job of
screening problem reports while also supporting and enhancing the
"Postgres culture", whereas a "bug report tool" eliminates that traffic
and requires one or a few people to pay attention to the bug list to
manage new and existing bug reports.
This has (or could have) a *huge* impact on the culture and tradition of
Postgres development, which imho is one of the most satisfying,
pleasant, and effective environments in open source development. So if
we try to do something with a bug tracking system, we will need to
figure out:
o how to retain a free and helpful discussion on the mailing lists, and
to not degrade into a "shut up and check the bug reports" response.
o how to filter or qualify bug reports so that developers don't spend
time having to do that.
All imho of course ;)
- Thomas