On Mon, Jan 28, 2013 at 8:19 PM, Giorgio Gentili
<[email protected]> wrote:
> Il 20/01/2013 23:35, Rob Weir ha scritto:
>
>> On Fri, Jan 18, 2013 at 6:12 PM, Giorgio Gentili
>> <[email protected]>  wrote:
>>>
>>> Hi,
>>> I completed check of the bug assigned to me , I confirmed only 2 bugs,
>>> the
>>> others, for different reasons, in my opinion are no more relevant.
>>> I would like to continue.
>>
>> Hi Giorgio, good work with the two confirmations.  The goal should be
>> to resolve all bugs, even the ones we can't confirm.  So how do we do
>> that?
>>
>> There are a few basic reasons why you might not be able to confirm a bug
>> report:
>>
>> 1) The bug is already fixed in the current release.  If that is true
>> you might be able to find the original bug report for the fixed bug by
>> searching Bugzilla.  But no guarantees.
>>
>> 2) The bug is intrinsically random.  For example, with memory
>> corruption, it might show up some times, but not others.
>>
>> 3) The user's instructions are incomplete and missing details needed
>> to reproduce the bug.
>>
>> 4) User error -- the misunderstand the product or ran into unrelated
>> issues (failing hardware, etc.)
>>
>> When you cannot confirm a bug, you need to decide what the next step
>> should be. Was the bug report incomplete missing details?  If so, post
>> a comment, explaining what steps you did and saying it worked for you.
>>   This might lead to an exchange of comments with the user as you
>> converge on a better understanding of what steps are needed to show
>> the bug.
>>
>> Or, if you think the bug report was clear and are confident that the
>> bug does not exist, then you can just mark the bug as
>> Resolved/Irreproducible.  Still explain what steps you tried and your
>> confirmation.  A bug report can always be re-opened if the user (or
>> someone else) can show how to reproduce it.
>>
>> So, one way or another you should indicate the next stage for the bugs
>> you reviewed.
>>
>> -- If it is a nonconfirm, but you are waiting for more info from the
>> user, then set the "needmoreinfo" keyword for the bug.
>>
>> -- if it is a nonconfirm and you are confident that there is no bug
>> here (already fixed, user error, etc.) then mark it as
>> Resolved/Irreproducible or Resolved/Invalid.
>>
>> Give that a try and I'll get you some new bugs to look at.
>>
>> Thanks!
>>
>> -Rob
>>
>>> Regards
>>> Giorgio
>
>
> Hi Rob,
> I completed, I hope in a satisfying way, my checks.
> Giorgio

Hi Giorgio, yes this looks great!

I'll send you some more reports to look at, OK?

-Rob

>

Reply via email to