About the only one that I could think to be a blocker would be the CNN bug since it's probably in the top10 pages, but I heard it also happens in firefox as well, so it may not even be our regression.
I think we also have a better handle on the ui_tests bug for Mac, at least in that we haven't seen it recently. I think that one can be downgraded to P1 if we want to keep it open for tracking. It doesn't seem to be causing the horrible ui_test failures it once was which makes it no longer a dev blocker. On Tue, Oct 27, 2009 at 4:49 PM, Peter Kasting <pkast...@google.com> wrote: > On Mon, Oct 26, 2009 at 9:41 PM, Anthony LaForge <lafo...@google.com> wrote: >> >> >> http://code.google.com/p/chromium/issues/list?can=2&q=pri:0&colspec=ID+Stars+Pri+Area+Type+Status+Summary+Modified+Owner+Mstone+OS&x=mstone&y=area&cells=tiles > > Most, if not all, of these, seem like P1 or lower to me. > P0 is supposed to mean "blocks work until it's fixed". Things like crashes > and regressions are generally P1 unless they're things like "100% crash on > start". > PK > > > -- Mike Pinkerton Mac Weenie pinker...@google.com --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
