[Cosmo-dev] nominating blocking bugs
mikeal at osafoundation.org
Mon Jan 22 14:03:37 PST 2007
> can you describe the chandler process? i'd always just assumed that P1
> & P2 bugs by definition were blockers.
We don't ship with P1 or P2 bugs, in a bind we'll punt P3 bugs at the
tail end of a release.
If you have a bug that is P3 and you know we can't ship without
fixing it you should nominate it for P1 or P2. At this time if a bug
is marked P2 and it's blocking some area of functionality or work it
should be bumped up to P1.
The "blocking" flag is really useful when a bug is blocking other
people who aren't assigned that bug. If a bug you are assigned is
only blocking you then you are aware enough of it to prioritize it
accordingly, but if someone else has a bug that is blocking or will
be blocking you it's nice to add an extra little decorator to let
people know how important it is to get it done so they can prioritize
it above other bugs that have the same priority status in bugzilla.
The blocking flag can also be used when a bug is blocking a large
enough area of functionality that QA can't test a feature set.
If I'm wrong Ted, Aparna, or Priscilla can correct me.
More information about the cosmo-dev