On Tue, Oct 27, 2009 at 4:04 PM, Anthony LaForge wrote:
> Moving forward, the TPMs are going to be more closely monitoring the P0 and
> ReleaseBlock-Dev (which we will treat effectively synonymously). Please
> help us to ensure labels on bugs are accurate.
This part in particular, I am happy ab
Thanks to everyone who helped (and indeed folks who are currently helping)
to clear theses issues. Indeed, re: the P0's the majority seemed to have
been mis-classified relative to the intent of what a P0 should represent and
have been demoted to P1.
Since all of the open issues have owners and ar
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 se
On Mon, Oct 26, 2009 at 9:41 PM, Anthony LaForge 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
Quick correction re: the "releaseblock-dev" issues, there are in reality 5
"label:releaseblock-dev" bugs. However even at 5, that level
is unacceptably high, particularly in the context of so many P0 bugs.
http://code.google.com/p/chromium/issues/list?can=2&q=label:releaseblock-dev&colspec=ID+Sta
