[Webkit-unassigned] [Bug 153194] [GTK] maps.google.com unresponsive/stalls in 2.11.3

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=153194

--- Comment #12 from Andres Gomez Garcia <agomez at igalia.com> ---
(In reply to comment #11)
...
> I already try as hard as possible to avoid introducing regressions, the fact
> that I prefer to fix 10 bugs instead of 5 and introduce 1 regression doesn't
> mean I'm careless when merging commits. And the key point, again is that I
> couldn't have avoided this regression just by being more careful. The only
> way to be more careful is having a bot that runs all the tests for every
> commit merged in the stable branch, but that would be a lot more work, and
> it woulnd't be enough either. Again this regression was not caught by our
> bots in trunk either. And of course I can't run all the tests for every
> merge myself, 2.10.5 took me 3 days full time merging commits, so I would
> need 3 weeks to do the same running the tests.

I think we are talking about different things. You are talking about running tests and I'm talking about having a space of time in which the changes introduced by the fixes are tested by real users.

That scenario I can only see that happening is if the changes are first introduced in an unstable release and enough time is left until being also merged in a stable release.

And I know that doing so doesn't guarantee that regression won't still be introduced but I think it is a change in the merging policy that can help a lot to prevent that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160122/be0ece34/attachment.html>