Re: Link to bug webpage

On Tue, Aug 21, 2001 at 09:51:29AM -0400, Bruce Momjian wrote:
> > >
> > >It's up to the group to decide.  If we have a database of bugs, I think
> > >it has to be complete.  I think a partial list is worse than no list at
> > >all.
> > >
> > 
> > I disagree. Unless you are omniscient, we will only ever have a partial list. 
> > 
> > Perhaps more importantly, the more common ones will be in the list, because
> > the more often it's reported, the more likely someone will use the bug
> > tool. If we develop a culture that says 'if it's on the bug list, it will
> > get looked at', then more people will report bugs via the correct channels
> > etc.
> 
> That is the real question.  Do we want to rely more heavily on a bug
> database rather than the email lists?  I haven't heard many say they
> want that.
> 

I think this is related to the discussions about what to do with
extensions, etc. The project is outgrowing its infrastructure. A bug
database is one of those things that is hard to justify and maintain
when all the developers can keep up with all the mailing lists, but
that hasn't been true for a while, now. The _need_ for a bug database
was recognized, but there wasn't enough interest for someone to take on
the maintenance.

As new developers have come in and taken over things like the JDBC
driver, and the ODBC driver, no one has the entire state of the code in
their head anymore. And, I think the project has reached critical mass:
attracting new developers is not a big problem - other projects are
taking PostgreSQL up as their base, without any selling from the core
developers. Perhaps trying again (either with the existing system,
or the PostgreSQL based Bugzilla) is the right answer. Personally,
I think a bug database that coordinates with the email archives is the
best of both worlds. That way, discussion about a bug, and it's state
all get archived in the same location, without a lot of extra bother on
the parts of the developers, just make sure to CC: the bug system.

Call for volunteers who wish to be involved in the maintenence, open up
the system, and put it on the list of TODO for release: 'check status
and usefulness of current bug reporting system' so it gets looked at
again at regular, appropriate intervals.

Ross