[Cosmo-dev] nominating blocking bugs

[Aparna Kadakia]

Brian,
Here's the document that explains how we use bugzilla for release  
management in Chandler.

http://wiki.osafoundation.org/Projects/ReleaseManagementWithBugzilla

Typically, when we set the blocking flag it means we block the  
release till the bug is fixed. They are generally set on certain P1  
bugs that we think are critical for the release. Under pressing  
conditions we might defer some P1s and P2s and release the product,  
but we would certainly not do that with outstanding blocker bugs.
Anyone can nominate a bug to be blocking the release(marked as  
blocking?). The bug council would go over them and mark them blocking 
+ or blocking- depending on the decision to hold the release for the  
bug or not.

Ted, +1 for setting the blocking flag in Cosmo.

Aparna


On Jan 22, 2007, at 1:05 PM, Brian Moseley wrote:

> On 1/19/07, Ted Leung <twl at osafoundation.org> wrote:
>
>> I just noticed that the Cosmo bugzilla does not have the blocking
>> flags that Chandler uses to nominate blocking bugs.   We need to find
>> a mechanism for people to nominate blockers.
>
> can you describe the chandler process? i'd always just assumed that P1
> & P2 bugs by definition were blockers.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev