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 > priority. > > I would suggest we use this way: > 1. Get candidate defects by query: severity = blocker, critical and status > = unconfirmed, confirmed, reopened > 2. Evaluate them and set/unset Flags as 4.0.0_release_blocker to get defect > list with high priority > 3. Assign these defects to development volunteers for fixing and QA to > verify once get resolved > > You comment and suggestion are welcome! >
Maybe someone can help clarify something: The BZ form has two fields for rating bugs: P1/P2/P3/P4 field and a blocker/critical/major/normal/minor/trivial field. What is the difference? Also, the 4.0 release blocker has 3 values: ?/+/-. The way we did it before was to set the field to "?" to propose it as a blocker, and then discuss it on the dev mailing list. If there was consensus it was a blocker then the value is changed to "+". -Rob > Regards, > Yu Zhen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
