On Tue, 21 Aug 2001, Bruce Momjian wrote:
> > > Yes, but we have to add items that don't come in through the database,
> > > and mark them as done/duplicates if we want it to be useful.
> >
> > Not necessarily. If someone discovers one that's not in the database
> > they'll add it. If it's already fixed it'll get closed out but will
> > still be in the database. It's not intended to be a todo/isdone list
> > or a development history reference. We have a TODO list and CVS for
> > that stuff.
>
> How do you communicate that to people looking at the content? Do you
> put in big letters at the top, "This list is not complete." The fact an
> items is missing from the list (new bug) is just as important as an item
> appearing on the list.
Huh? A list of bugs is only as complete as those submitting to it ... its
no more, or less, complete then a mailing list *shrug*
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
