Hi Arjan, On 6/29/11 4:41 PM, "ext Arjan van de Ven" <[email protected]> wrote:
>On 6/29/2011 2:05 AM, [email protected] wrote: >> So I guess you could remind anyone on your side involved into moving the >> bugs that it's mandatory to at least put a comment with the reasoning >> behind the action. > >so as a user of bugzilla I strongly disagree with your statement. >I use the "filter bug mail" feature so that I only get bugmail on >important events (real new information added, not just noisy bookkeeping >things) >that feature gets completely and utterly destroyed if the QA person, in >addition to the actual change, also puts in "I changed this" as comment. >(and that comment adds absolutely zero value) 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 agree some of the QA activities may not bring added value to the report itself and if too many alter the readability but I think moving bugs deserves clear documentation e.g. Why someone makes decision to move it... BR, Eric _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
