[Chandler-dev] Checkin process when the tree isn't green?

[Bryan Stearns]

Heikki Toivonen wrote:
> Bryan Stearns wrote:
>   
>> [proposal for a strategy to switch to when the tree has been yellow for an extended period]
>>     
> I still disagree. Here's why. If we strictly follow the checkin rules
> doc, we will not have a situation where the tree is orange for longer
> than half a day, maybe a day at most. There won't be a long list of
> checkins to investigate and back out; we'll just back out if it has gone
> for that long.
>   
I'm not proposing that we change the normal policy - I'm saying there's 
a need for a different strategy when the tree's been yellow for more 
than, say, a week.

You're saying "We don't need fire hydrants - fire extinguishers are fine 
for keeping small fires from becoming large fires." I'm saying "The 
entire building is engulfed - clearly, fire hydrants would be useful in 
situations like this". :-)

> What I don't understand is the extreme displeasure some people express
> even at the mention of backing out bad changes. It is easy to backout,
> and easy to recommit with fixes, and it will make the tree green
> quickly. Why is this bad?
>   
I have no problem with backing out very recent changes, but blindly 
backing out older changes will lead to the snowball effect I mentioned, 
because later changes often assume previous changes. Once this happens, 
it can become hard to figure out what changes are in and which aren't.
> I'd like to hear opinions from other people as well. What is your
> preference to deal with tree breakage in general, and this current
> situation?
I'd also like to hear from others. Since no one else has responded, I 
feel like I'm the only one troubled by this problem - is everyone else 
happy just ignoring the rules?

...Bryan