On Wed, Jun 14, 2017 at 10:49 AM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> On 6/14/17 12:23 PM, Andrew Swan wrote: > >> I would hope that if we have promising or widely used webextension >> experiments, that the relevant peers would be aware of them when reviewing >> changes that might affect them >> > > I don't see how they would be, unless we have something like dxr for the > relevant code. > > As a concrete example, how would a necko peer know that some webextension > experiment uses or doesn't use various necko interfaces? Sorry, this was misleading, I meant this as a narrow comment about the (still hypothetical!) scenario where something is prototyped as an experiment but we're in the process of landing it in m-c along with all the other built-in apis. Of course we can't/don't expect reviewers to be aware of every small experiment that is out there. And again, we've communicated to extension developers that they cannot rely on stable internal interface. And finally, I agree with sfink and nfroyd that the only way to really be able to depend on experiments at a larger scale is to get them into automation. I personally pledge not to complain about any changes that break out-of-tree code until then... :) -Andrew _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
