On Feb 8, 2010, at 5:33 PM, Dimitri Glazkov wrote: > Do you guys think it may be a good idea to bring the concept of tree > closure to WebKit?
I'd like to start with more active broadcast notification of build breaks and see if we think we need more changes from there. I prefer to try technology-based approaches before process-based approaches. Right now broken trees linger because you have to go out of your way to notice, meaning the information diffuses slowly. Regards, Maciej > > :DG< > > On Mon, Feb 8, 2010 at 5:29 PM, Maciej Stachowiak <m...@apple.com> wrote: >> >> On Feb 8, 2010, at 4:45 PM, Eric Seidel wrote: >> >>> Historically build.webkit.org would email people when their changes >>> broke the tree. This was disabled some time ago. >>> >>> I would very much like to see it re-enabled. Could someone point me >>> as to how that would happen (I'm happy to code up a patch), or flip >>> the magical switch themselves? >> >> I'd actually like to see it email a mailing list, in addition to the >> individuals it guesses are to blame. That could be either webkit-dev or a >> new list. Maybe some won't want the spam but I bet a lot of people would >> like to find out about every build break. If it's at all possible, it would >> be great to email all of the patch author, the reviewer and the committer >> (if different from the patch author). >> >> I also think it would be neat if we could have a bot that alerts about build >> breaks on IRC in #webkit. >> >> And finally, it might be good to have extra notice if a build remains broken >> for some time (every 24 hours maybe?) >> >> Regards, >> Maciej >> >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
