"H.Merijn Brand" wrote:
>
> > > poor soul that has to detect those ... Yes, it's a lot of work, and it's not so
> > > long ago that we did a cleanup with common effort. Let's keep the open bug
> > > count as low as possible, which also motivates bug diggers to pick up open bugs
> > > to fight.
Hear hear.
> > The issue here seems to be that as we automate more and more the process
> > of reporting build failures, we're flooding the bugdb with lots of
> > hard-to-seperate-out reports. Perhaps it's time to add a category to the
> > bugdb to support these tests? I don't expect that automatic build testing
> > is going to cease any time soon, but nor do I believe that each automatic
> > build report should become an open bug.
> >
> > Suggestions?
> >
By all means have another bugdb.
_IF_ you do want to continue to use the current bugdb, you could
consider sending
a mail to [EMAIL PROTECTED] with the following (nearly inherent)
hints:
category=dailybuild
status=open|closed
severity=fatal|high
etc.
My point is that you should be able to set the category to whatever you
like (start a new one today), and then you can assign any bug to any
other
bug as a parent/child and/or duplicate.
Please note that the address won't work until I set up a .qmail pointer,
just say the word, the rest is already in place.
I don't know if that's useful to you or not, but at least you then have
an
inter-related set of records.
???
Ciao
--
Richard Foley
Ciao: shorter than Aufwiedersehen
