On Tue, Apr 23, 2013 at 8:41 AM, Chris AtLee <cat...@mozilla.com> wrote: > We've considered enforcing this using some cryptographic token. After you > push to try and get good results, the system gives you a token you need to > include in your commit to m-i.
Sounds like the goal of this kind of solution would be to eliminate the "developer made a bad judgement call" case, but it's not at all clear to me that that problem is worse than "developer overuses try for trivial changes" or "developer needs to wait for try results before pushing trivial fix" problem. It's also not at all clear to me that a 13% backout rate on inbound is a problem, because there are a lot of factors at play. Those backouts represent "wasted resources" (build machine time, sheriff time, sometimes tree-closure time), but if the alternative is wasting developer time (needing to wait for try results unnecessarily) and tryserver build machine time, the tradeoff becomes less clear. Obviously different perspectives here also impact your view of those tradeoffs. Gavin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
