Very much agreed. If anything is red, and it's not immediately clear
that someone's on it, close the tree. The burden should be on whoever
is explaining why the tree is open but red, not why it's closed,
especially for the sheriff.
--Amanda
On Wednesday, August 5, 2009, Peter Kasting <pkast...@google.com> wrote:
> On Wed, Aug 5, 2009 at 2:45 PM, Tim Steele <t...@chromium.org> wrote:
>
> A constant place to go looking for this would make it easier, at least in my
> opinion. Like right now I don't know what's up with Chromium Mac (valgrind)
> or Webkit dbg (1&2) to name a few; they're red but the tree is open.
>
> If you ever see a case like this, go ahead and close the tree yourself until
> you get an explanation for every bit of redness. Then put the explanation
> into the tree status.
> I know people hate having the tree closed, but we need to be hard-nosed about
> closing it for _anything_ red.
>
> PK
> >
>
--
"Portability is generally the result of advance planning rather than trench
warfare involving #ifdef" -- Henry Spencer (1992)
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
