[webkit-dev] Rolling out a patch requires a justification beyond a test failure in downstream projects

[David Levin]

Was this an isolated incident then?


On Tue, Dec 11, 2012 at 8:39 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:

> On Tue, Dec 11, 2012 at 1:44 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
>
>> First off, I don't think we should be rolling out patches based solely on
>> a downstream test unless there is a clear evidence that the failure is a
>> real regression in WebKit that affects more than just the said downstream
>> project.
>>
>
> To understand this perspective, imagine that I've created a new app called
> SuperWebKitApp that's built on Chromium, EFL, GTK+, Qt, etc... ports in my
> spare time, and started rolling out all Chromium, EFL, GTK+, Qt, etc...
> patches that break automated tests in SuperWebKitApp, just giving
> hyperlinks to my buildbots. That's pretty upsetting, isn't it?
>
> - R. Niwa
>
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20121211/8093c110/attachment.html>