← Back to team overview

launchpad-dev team mailing list archive

Re: marking as dup - always use oldest bug?

 

Sorry, quick click fail.

Was meaning to say....

On Wed, Jan 12, 2011 at 9:35 AM, Deryck Hodge
<deryck.hodge@xxxxxxxxxxxxx> wrote:
> On Wed, Jan 12, 2011 at 7:57 AM, Aaron Bentley <aaron@xxxxxxxxxxxxx> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 11-01-10 01:35 PM, Robert Collins wrote:
>>> On searches:
>>>  - the dupe finder is *meant* to search across dupes too, if its not
>>> thats a bug - lets confirm and file it.
>>
>> I don't know about the dupe finder, but I know that the standard bug
>> search is not finding the authoritative bug if it doesn't have a bug
>> task for project you filed the dupe on.
>>
>> I filed #699891 on oops-tools, and it was marked as a dupe #661266,
>> which was an Apache OpenID bug.  Afterward, searching "openid" on
>> "oops-tools" found nothing.
>>
>>>  - to workaround such a bug we can simply edit the title and body of
>>> the older bug - and we should do that as part of keeping the bug
>>> maintained. They should be living documents.
>>
>> I thought that was the issue at first, but I found that adding "openid"
>> to #661266 title did not make it possible to find it using a bug search
>> on oop-tools.  So I added a bug task on oops-tools.
>>

This makes sense to me actually.  The bug was moved off one project to
another in a sense.  I'm assuming also it did it not show up even when
un-selecting "hide duplicate bugs" from the advanced search, right?

I guess I'm not sure if this is a bug or a feature. :-)  Half-kidding,
of course, but I hope you all get my point.

Cheers,
deryck


-- 
Deryck Hodge
https://launchpad.net/~deryck
http://www.devurandom.org/



References