All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Bug Verify
Date: Mon, 13 Dec 2010 12:07:20 +0000	[thread overview]
Message-ID: <1292242040.2485.8.camel@scimitar> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D5A7A1692@shsmsx502.ccr.corp.intel.com>

On Mon, 2010-12-13 at 19:56 +0800, Tian, Kevin wrote:
> >From: Joshua Lock
> >Sent: Monday, December 13, 2010 7:49 PM
> >
> >On Mon, 2010-12-13 at 17:20 +0800, 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've just gone through and verified the bugs I've filed. I think we
> >could make this process easier to remember if we had a shared saved
> >search "bugs I need to verify"?
> >
> 
> You should be able to save that search under your account directly... :-)

Of course, but I can only create a saved search for myself (and I now
have that).

However, I was assuming the bugzilla admin could create a search which
would show the logged in user all of their bugs which need verifying.

Just trying to think of ways to make this process more obvious for the
team.

Cheers,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre



  reply	other threads:[~2010-12-13 12:07 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 [this message]
2010-12-13 12:08       ` Tian, Kevin
2010-12-13 16:47 ` Scott Garman
2010-12-13 18:01   ` Bruce Ashfield

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=1292242040.2485.8.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=kevin.tian@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.