launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #06156
Re: marking as dup - always use oldest bug?
On Mon, Jan 10, 2011 at 9:54 AM, Graham Binns <graham@xxxxxxxxxxxxx> wrote:
> On 10 January 2011 15:46, Julian Edwards <julian.edwards@xxxxxxxxxxxxx> wrote:
>> On Monday 10 January 2011 15:28:03 Robert Collins wrote:
>>> Just in the context of saying we should work on the oldest of two
>>> bugs, all other things being equal - that implies to me that we
>>> probably want to dup things onto the oldest duplicate, so we don't
>>> perturbate the queue unnecessarily.
>>>
>>> What do you think?
>>
>> It's a good idea, we just need to be careful as I've seen the newest one used
>> as it's had more info/comments on it. They're easily lost if you only see the
>> older one.
>>
>
> +1. I use "dupe to the oldest, unless better data is available later"
> as a rule of thumb.
This is my approach, too. So I think Rob's "all other things being
equal" is the key phrase. If a newer bug is better, we shouldn't be a
slave to the rule.
Cheers,
deryck
--
Deryck Hodge
https://launchpad.net/~deryck
http://www.devurandom.org/
Follow ups
References