From: Darren Hart <dvhart@linux.intel.com>
To: "Serban, Laurentiu" <laurentiu.serban@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: VERIFIED vs CLOSED in yocto bugzilla
Date: Tue, 19 Jun 2012 16:22:44 -0700 [thread overview]
Message-ID: <4FE109C4.1010906@linux.intel.com> (raw)
In-Reply-To: <E16513A01CAAFF40B65178C63CE45EEC1914D426@IRSMSX102.ger.corp.intel.com>
On 06/19/2012 12:25 PM, Serban, Laurentiu wrote:
> Hello,
>
>
>
> I submit to your attention the following issue related to Yocto
> project’s bugzilla:
>
>
>
> Which is the most appropriate end for a the lifecycle of a bugzilla
> issue: VERIFIED or CLOSED?
>
> Currently the bug lifecycle final point is VERIFIED and the status
> CLOSED is not used. Setting a bug to CLOSED after it was VERIFIED has no
> impact on the lifecycle itself as the bug can be reopened anyway.
>
>
>
> My proposal is the following: keep VERIFIED as the final point of the
> bug lifecycle and use the status CLOSED for the bug only after the 1.3
> release, *if* the regression testing for the bug is ran and passed.
>
> So after the 1.3 release the ideal situation is that all the bugs
> related to it with previous status VERIFIED are CLOSED.
What is the reasoning driving this change? What does CLOSED indicate
that VERIFIED does not already convey?
Thanks,
Darren
>
>
>
> Waiting for your opinion on this,
>
> Thank you,
>
>
>
> *Laurentiu Serban*
>
> QA Engineer
>
> Open Source Technology Center
>
> System Software Division Romania
>
> Desk: +40 31 8604742**
>
> iNET: 88451042
>
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-19 23:24 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 [this message]
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
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=4FE109C4.1010906@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=laurentiu.serban@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.