On Fri, Sep 04, 2009 at 02:02:46PM -0400, Mateo Murphy wrote: > > > On 4-Sep-09, at 12:55 PM, Chad Woolley wrote: > > > However, not fixing the build promptly is a problem, and one of the > > reasons I wanted to reinstate notifications to this list. > > > > On a large/distributed project like Rails - especially one where many > > people run the master branch live in their projects - I believe there > > are exactly three appropriate responses to a broken build, in order of > > decreasing desirability: > > > > 1. Fix the failing tests, ASAP > > 2. Roll back the change which broke the tests, ASAP > > 3. Comment/disable the failing tests, ASAP > > The problem is that, unless I'm mistaken, the majority of the people > on this list don't have commit rights, so we're unable to do any of > these things ASAP. The value of having the notifications sent out to > non committers is quite limited, which is why it would be nice to be > able to opt out.
Perhaps a timeout within which the build should be fixed? I mean it doesn't take hours for CI to detect the problem. And then mail if fix doesn't come in time. I don't believe committers will want to create and subscribe to a separate list. And this is *their* mailing list. Then again, the rest of us may want to know if we should "pull" or not. -- Cezary Bagiński --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
