Re: Cloning bugs: Just Don't Do It

2015-11-04 Thread Kevin Fenzi
On Tue, 3 Nov 2015 18:25:32 + Jonathan Underwood wrote: > Mostly agreed. The one legit use-case though is when someone wants to > to continue a package submission after a review has gone dead due to > the original submitter vanishing. There's often useful

Re: Cloning bugs: Just Don't Do It

2015-11-04 Thread Jonathan Underwood
On 4 November 2015 at 14:31, Kevin Fenzi wrote: > On Tue, 3 Nov 2015 18:25:32 + > Jonathan Underwood wrote: > >> Mostly agreed. The one legit use-case though is when someone wants to >> to continue a package submission after a review has gone

Re: Cloning bugs: Just Don't Do It

2015-11-03 Thread Kevin Fenzi
On Tue, 3 Nov 2015 11:37:34 -0500 Josh Boyer wrote: > On Tue, Nov 3, 2015 at 11:36 AM, Kevin Fenzi wrote: > > +1000 > > > > Additionally, I find people clone bugs with the idea that some kind > > of similar change/fix needs to be made in a different

Re: Cloning bugs: Just Don't Do It

2015-11-03 Thread Jonathan Underwood
On 3 November 2015 at 16:13, Adam Williamson wrote: > You see that 'Clone' button in Bugzilla? You, yes you, with your cursor > hovering over it? > > Don't do it! It's a trap. > > Cloning a bug is almost never actually what you want to do. When you > clone a bug, all

Cloning bugs: Just Don't Do It

2015-11-03 Thread Adam Williamson
You see that 'Clone' button in Bugzilla? You, yes you, with your cursor hovering over it? Don't do it! It's a trap. Cloning a bug is almost never actually what you want to do. When you clone a bug, all of the following are transferred to the new bug: 1. CCs 2. Description and comments, as one

Re: Cloning bugs: Just Don't Do It

2015-11-03 Thread Kevin Fenzi
+1000 Additionally, I find people clone bugs with the idea that some kind of similar change/fix needs to be made in a different package. Don't do that. It's often impossible to tell why the clone was even made or what action the cloner is expecting (leading to several round trips back and forth

Re: Cloning bugs: Just Don't Do It

2015-11-03 Thread Josh Boyer
On Tue, Nov 3, 2015 at 11:36 AM, Kevin Fenzi wrote: > +1000 > > Additionally, I find people clone bugs with the idea that some kind of > similar change/fix needs to be made in a different package. Don't do > that. It's often impossible to tell why the clone was even made or what

Re: Cloning bugs: Just Don't Do It

2015-11-03 Thread Rich Megginson
On 11/03/2015 09:13 AM, Adam Williamson wrote: You see that 'Clone' button in Bugzilla? You, yes you, with your cursor hovering over it? Don't do it! It's a trap. Cloning a bug is almost never actually what you want to do. When you clone a bug, all of the following are transferred to the new

Re: Cloning bugs: Just Don't Do It

2015-11-03 Thread Michael Catanzaro
On Tue, 2015-11-03 at 08:13 -0800, Adam Williamson wrote: > You see that 'Clone' button in Bugzilla? You, yes you, with your > cursor > hovering over it? > > Don't do it! It's a trap. As long as the button exists, people will use it -- devel mailing list devel@lists.fedoraproject.org