On Thu, 2010-06-17 at 14:25 -0400, Matt McCutchen wrote: > On Thu, 2010-06-17 at 11:13 -0700, Adam Williamson wrote: > > RHEL bugs are frequently created as clones of Fedora bugs, and whoever > > cloned the bug forgets to clean up behind them. For instance, if you > > clone a Fedora bug which blocks F14Blocker to RHEL and forget to clean > > up, we wind up with a RHEL bug 'blocking' the Fedora 14 release. > > You're saying the clone by default blocks the same bugs as the original? Yup, in my experience that's what happens. Clone in Bugzilla really means *clone*: it copies just about every attribute of the initial bug to the new one, including the entire comment history as the initial 'description'. > I think it would make more sense if the clone did not block any bugs > initially. Would someone care to test what the latest upstream Bugzilla > does? > > > Often clones also leave the CC list intact, meaning a bunch of Fedora > > users are suddenly CCed on a high-traffic RHEL bug. > > Yes, I filed a bug on that: > > https://bugzilla.redhat.com/show_bug.cgi?id=582347 I suspect it's not really a bug. I think Bugzilla intends the clone feature to really be a clone feature, and people don't think hard enough about the implications of that... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
