From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Darren Hart <dvhart@linux.intel.com>
Subject: Re: VERIFIED vs CLOSED in yocto bugzilla
Date: Wed, 20 Jun 2012 08:48:59 -0700 [thread overview]
Message-ID: <4FE1F0EB.9060806@linux.intel.com> (raw)
In-Reply-To: <CAMKF1spPQ2nJqJPj7fG0rWKqQ1v0xZoahx03a8W66yXzKCcSsA@mail.gmail.com>
On 06/20/2012 08:27 AM, Khem Raj wrote:
> On Wed, Jun 20, 2012 at 2:18 AM, Burton, Ross<ross.burton@intel.com> wrote:
>>
>> Agreed -- hiding CLOSED would be my proposal as it doesn't add any
>> meaning, just complicates the lifecycle.
>
> I think yes hiding closed it ok since it does not change much in fix.
> I wouldnt say it complicates but it completes the life cycle
> since the owner for closing action is submitter. it closes the life
> cycle nicely.
The bug verification is the responsibility of the submitter, not the
assignee/owner. So there could be 2 actions here, one is the submitter
has verified this (added any test cases to testoipa for future
regression testing. The second is, as Laurentiu suggests, marking closed
by the QA team when releases does it's final regression testing.
So yes, I could see hiding CLOSED and leaving the final state as
VERIFIED, but I can see further value of using the CLOSED state to
indicate that it passed regression at the end of the release cycle.
So this should also act as a reminder to submitters to "verify" there bugs!
Sau!
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
next prev parent reply other threads:[~2012-06-20 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 19:25 VERIFIED vs CLOSED in yocto bugzilla Serban, Laurentiu
2012-06-19 20:19 ` Khem Raj
2012-06-19 23:22 ` Darren Hart
2012-06-20 7:12 ` Serban, Laurentiu
2012-06-20 9:18 ` Burton, Ross
2012-06-20 15:27 ` Khem Raj
2012-06-20 15:48 ` Saul Wold [this message]
2012-06-20 15:55 ` Khem Raj
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=4FE1F0EB.9060806@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=raj.khem@gmail.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.