OOPS frequency is only indicated by the frequency column

[Diogo Matsubara]

Oops reports should use color codes (green, yellow, red) to denote its importance
For instance, if we get more than 20 exceptions or more than 100 timeouts or more than 20 UFD or more than 25 ProtocolExceptions, that oops report should have an Yellow code in the subject line indicating its importance

Similar to what is used in the terrorism threat color codes <http://en.wikipedia.org/wiki/Homeland_Security_Advisory_System>

[Francis J. Lacoste (flacoste)]

Well, the Homeland is probably not a good example, because in practice there are only two levels: Orange or Red! I

[Diogo Matsubara (matsubara)]

re-targeting to 1.2.6

[Joey Stanford (joey)]

delayed until 2.x

[Christian Reis (kiko)]

Not really high importance if it hasn't been done yet.

[Robert Collins (lifeless)]

I think this is saying that we should set a threshold at which oopses become more bad :) I think this is probably to shallow - different oopses have different tolerance levels - and we are aiming to have 0 oopses altogether. So, this is an itch-scratching bug rather than a feature we need.