[yocto] VERIFIED vs CLOSED in yocto bugzilla

[Serban, Laurentiu]

The discussion was triggered in the Yocto Project Technical Team Meeting from June 19th.


-----Original Message-----
From: Darren Hart [mailto:dvhart at linux.intel.com] 
Sent: Wednesday, June 20, 2012 2:23 AM
To: Serban, Laurentiu
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] VERIFIED vs CLOSED in yocto bugzilla



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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel