Re: [help]] my first bug triage

[Elijah P Newren <newren math utah edu>]

> Dear Gnome Bugsquad,
>
> Hi! My name is Johnny (IRC handle jkl) and I am very pleased to join
> all of you in contributing to the Gnome project.

Welcome Johnny.  :)

> ...so I need your help in reviewing my
> proposed changes for my very first bug triage:
>
> [Link to bug]
> http://bugzilla.gnome.org/show_bug.cgi?id=111969
> Status: UNCOFIRMED
>
> I would like to add the following comment and change its status
> correspondingly:
> 
> ----- BEGIN COMMENT -----
> Looks like a duplicate of <a
> href="http://bugzilla.gnome.org/show_bug.cgi?id=104260";;>bug
> 104260</a>.
> 
> Changing state from UNCONFIRMED -> Duplicate of bug #104260
> ----- END COMMENT -----

Hmmm.  You are definitely correct, but you did bring up a couple things
that I obviously neglected for the extended triage guide.  Bugzilla will
automatically add the html commands for certain strings.  Thus adding a
comment that says
   This appears to be a dup of bug 104260.
Would result in bugzilla adding the html code of
   This appears to be a dup of <a href =
    "http://bugzilla.gnome.org/show_bug.cgi?id=104260";>bug 104260</a>.
being added to the bug.  Also, obvious URLs also have html code
automatically added for them, thus
   http://www.gnome.org
becomes
   <a href="http://www.gnome.org>http://www.gnome.org</a>

Also, it appears that you've added a comment to bug 104260, and
attempted (and succeeded) to make it look exactly like the comment that
bugzilla automatically adds when one bug is marked as a duplicate of
another.  Unfortunately, it can serve to be a little confusing, since
now when bug 111969 is marked as a duplicate of 104260, it's going to
have another identical comment placed in it.

> I came to this conclusion by using the simple-dup-finder and then
> using the screenshot-comparison method of the two backtraces. Any
> feedback/help on making this change will be appreciated.

By screenshot-comparison method, did you actually take the screenshots?
If so, perhaps I need to clarify that part of my howto.  The point was
that I simple open up both bugs in two separate tabs, scroll them both
down the the appropriate point, and then switch back and forth.  Since I
couldn't get the bug reports saved in html format to automatically
scroll down to the right place for everyone, I put screenshots of having
done that in the guide.  Of course, I'd like this guide to work for the
not-so-technically-talented (e.g. my wife), so even if you didn't
actually take the screenshots, perhaps I should add a comment clarifying
that...

> Thanks and talk to you soon! :)

Thanks for helping out and catching this duplicate for us!

I went ahead and added a comment to 111969 and marked it as a
duplicate.  Just for future reference, here's the entire Additional
Comment that I added to the box (the rest is added by bugzilla when I
select the "Resolve bug, mark it as duplicate of bug #" stuff in the
"Change State or Resolution" box):

   Thanks for the bug report. This particular bug has already been
   reported into our bug tracking system, but please feel free to report
   any further bugs you find.

Elijah (a.k.a. fuzz)

-- 
-----------------------------------------------------------------
Elijah Newren
Internet: http://www.math.utah.edu/~newren   newren math utah edu
Tired of pop-up webpages when surfing the internet?  Look at
   http://www.math.utah.edu/~newren/noPopUps.html
for how to get rid of them without spending a penny.
-----------------------------------------------------------------