Thanks for your comment, here is the updated process based on the feedback
1. Get candidate bugs by query: severity = blocker, critical and status =
unconfirmed, confirmed, reopened OR keyword includes crash.
2. For every candidate bug above, set field 4.0 release blocker to ?
to propose it as a
Yuzhen Fan wrote:
Thanks for your comment, here is the updated process based on the feedback
1. Get candidate bugs by query: severity = blocker, critical and status =
unconfirmed, confirmed, reopened OR keyword includes crash.
Regressions are also candidates for fixing in the next release. So
On Wed, May 8, 2013 at 8:54 AM, Yuzhen Fan fanyuz...@gmail.com wrote:
Hi,
We have pretty high backlog for unresolved defects, we need to clean them
as much as possible before we exit full regression. Before we focus on the
fixing work, let's set the filter and get the defect list with high
On Wed, May 08, 2013 at 08:54:59PM +0800, Yuzhen Fan wrote:
Hi,
We have pretty high backlog for unresolved defects, we need to clean them
as much as possible before we exit full regression. Before we focus on the
fixing work, let's set the filter and get the defect list with high
priority.
hi,Rob
I inform Priority and Severity fields from BZ help
1.
*Priority:* The bug assignee uses this field to prioritize his or her
bugs. It's a good idea not to change this on other people's bugs.
2.
*Severity:* This indicates how severe the problem is - from blocker
