On 1/2/09, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > Jerry Amundson wrote: >> 1. The hard line approach - CLOSE it and cite the bug writing >> Principles page[2], specifically, "One bug per report". (noticeably >> *absent* from bugs.kde.org) > > I'd suggest doing that. I'm really fed up of "everything but the kitchen > sink" type bug reports. Those are always a PITA to work with as a developer > because you never know when to close them. > > IMHO, "Please file n separate bug reports for your n separate issues. Thanks > in advance!" is enough of a form letter. I've added a section with a smoothed out version of that. [1] Thanks for leading the way with my upstream example. [2] :-) jerry [1] https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#Two_or_more_issues_per_report [2] http://bugs.kde.org/show_bug.cgi?id=171832 -- To be named later. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
