From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Bug Verify
Date: Mon, 13 Dec 2010 13:01:48 -0500 [thread overview]
Message-ID: <4D065F8C.4050102@windriver.com> (raw)
In-Reply-To: <4D064E22.8060003@intel.com>
On 10-12-13 11:47 AM, Scott Garman wrote:
> On 12/13/2010 01:20 AM, Yu, Ke wrote:
>> Hi,
>>
>> I hate to raise this question, but there is still bunch of bugs that
>> is fixed but not verified. According to the process, it is reporter's
>> responsibility to verify the bug, so could I ask the reporter's help
>> on this? Process is sometime tedious but helpful to quality
>> assurance. Thanks a lot for your effort.
>
> I have now verified all my bugs.
>
> However, the process doesn't seem right to me. As the person who fixed
> the bug, presumably I performed verification that my fix actually works,
> which is why I marked the bug as fixed to begin with.
>
> At every other company I've been with, bug verification is performed by
> the QA team - and I think the purpose of it is to ensure someone other
> than the developer who fixed the bug can independently verify the bug is
> indeed resolved. A second pair of eyes can spot new problems more easily.
I'd second Scott's opinion here. I wasn't marking my bugs
as verified, since as a submitter, I've never had to do
this in 10+ years in the 'biz'.
Cheers,
Bruce
>
> JMO,
>
> Scott
>
prev parent reply other threads:[~2010-12-13 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 9:20 Bug Verify Yu, Ke
2010-12-13 11:48 ` Joshua Lock
2010-12-13 11:56 ` Tian, Kevin
2010-12-13 12:07 ` Joshua Lock
2010-12-13 12:08 ` Tian, Kevin
2010-12-13 16:47 ` Scott Garman
2010-12-13 18:01 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D065F8C.4050102@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=scott.a.garman@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.