On Fri, Oct 2, 2015 at 6:49 PM, Justin D'Arcangelo <[email protected]> wrote:
> I would also like to add that this policy of immediately pouncing on devs > who attempt to try something new Pouncing on devs should never be acceptable... unless a robot is doing it! In all seriousness, while I'm fully on the "The way to make a program faster is to never let it get slower." [1] boat we don't have the infrastructure (yet) to back that claim. Even extra cautious devs like Justin (who ran raptor tests locally) get noisy results from the latest gecko regression. My point is, we can cheerfully talk between humans, make compromises and change course. Or we can have bots doing aggressive backouts / pre-landing checks (here's a nice read for the weekend [2]). But aggressive email exchanges between team members won't make our phones any better. [1] http://www.webkit.org/projects/performance/ [2] https://code.facebook.com/posts/924676474230092/mobile-performance-tooling-infrastructure-at-facebook/ PS: Eli's original message was super nice and useful and I know the raptor team is working really hard to automate more of this! <3
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
