On Tue, 2009-09-08 at 08:51 +0200, Niels Haase wrote: > 2009/9/7 Sergey Rudchenko <sergey.rudchenko@xxxxxxxxx>: > > > Is there a generic model how to process (or split) such bugreports? I > > mean, how long such bug would live unassigned (assume the mentioned > > problems persist). I see this as a dead-end. Only stock comment doesn't > > move the bug to the resolution, does it?. > > > > The correction of this behaviour should be done by the reporter of the > bug. Split the bug and reopen from a triager might be not the best > idea, since from now on you are the reporter and all "NEEDINFO" flags > are opened against you in this case. But again, the "Two or more > issues" is more the case that Reporter A opens a bug e.g X fails with > Voodoo 3 and Reporter B ad a comment that his/her X is also falling > bit with a Voodoo 6 Card. Same symptom, but different cards. But > again, in this bug, it seams all related to gdm and also linked to the > same problem. The important question to ask yourself is whether one problem could be fixed without the other being fixed. This is the underlying reason why multiple reports in one bug are bad: because it makes tracking impossible. If a bug covers two issues, and one's fixed but the other isn't, do you mark it as FIXED or ASSIGNED? Impossible choice. If a report covers somewhat different but related issues like this, and it's unlikely the maintainer would fix one but not the other, you can leave it as one report. To some degree it's up to triager and maintainer discretion (and, as in all cases, maintainer discretion overrides triager discretion, so if your maintainer has a definite opinion on how it should be handled, defer to them). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
