Re: [QA] To clone or not to clone ( a bug report ) that's the question...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2009-01-21 at 21:46 +0000, "Jóhann B. Guðmundsson" wrote:
>  
> A.
>      File the same bug 3 times as in once for each release?

I'd prefer A.  My reasons:

  1) the same "bug" may be caused by different things in different
releases.  Not every package has the same code for the entire release
family.

  2) different sets of users care about bugs in different release trees.
Closing a bug as fixed->rawhide doesn't help the user who is hitting
this issue on say F-9.

  3) bodhi auto-closing.  Not every update gets pushed at the same time,
and closing a single bug when an F-10 update goes out doesn't help the
F-9 users know that the update for their release has gone out, or been
delayed, or just not provided.

  4) The maintainer is the right person to decide if the bugs should be
collapsed into one, rather than the triager trying to make a judgement
call.  It's easier to close->dup than to clone in the first place, if
all the above doesn't apply.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux