Hi Arjan, On 6/30/11 4:41 PM, "ext Arjan van de Ven" <[email protected]> wrote:
>On 6/29/2011 11:57 PM, [email protected] wrote: >> >> I hear you but isn't moving a bug to another component an important >>enough >> event it's worth recording it in an inline comment on the bug? > >I would say not. the component is metadata and does not add value to the >bug itself.... >it doesn't help in any way shape or form in getting it fixed. > >I have a very simple idea on bugs; the value of a bug lies in its >ability to fix something in the OS >that makes the OS better. Anything else around the bug is either neutral >or overhead. > >it's not just about the readability of the bug itself (which is >important); it is about the readability >of my, and every developers, bugzilla email folder. If the >signal-to-noise ratio of that folder is not >high enough, I'm sorry but it will get ignored. > > >Changing some bits in a database, which are just bits on a spinning >piece of rust, that has the effect >of changing components does not add value in any way, shape or form in >my definition of bug value above... >... and thus is "noise" in the bug mail folder. Now that you put it this way, I'm more than convinced that nothing but value should matter in bug reports though I'm a bit skeptical on what it actually means for other target population than developers. Hopefully, QA and other average users won't contribute too much to what can be perceived as noise with their activities, questions ,etc... Cheers, Eric _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
