On 4/11/07, Federico Mena Quintero <[EMAIL PROTECTED]> wrote: > This is totally awesome :) I didn't know our Bugzilla infrastructure > was so nice.
Olav rocks. :-) > > But to avoid false-positives, we require human intervention (and only > > a few people have the appropriate privileges) involving manual entry > > of data that should uniquely match the given bug. > > OK. What sort of data would you need? Or can it be inferred from (say) > a bunch of duplicate bugs? edittraces.cgi currently asks for 1) Product 2) Product version (can be blank, makes comparison test ignore this field) 3) GNOME version (can be blank; bug-buddy can't always detect GNOME version) 4) Complete stack trace 5) Reason (explanatory text sent to user when report is rejected) I didn't develop it and haven't yet used it myself; further questions are probably best directed to Olav or perhaps Andre or Karsten. > > If you have such a > > bug you'd like put on the auto-rejection list, contact the bugsquad > > with the information about the bug and a specifically tailored message > > you want bug-buddy to show the user. > > This is great to know. Is there a way we can notify all maintainers > about this? Good question. I have no idea. Cheers, Elijah _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
