Opinions vary.
From my point of view, if we attempt another subsystem transplant across a
code boundary that lacks clean separation (e.g., parallel layout), then we
will continue to need this coupling in the future.
If we instead get to a point where most of the modules that Firefox is
using from Servo have relatively stable APIs, the two projects each have
their own product ship cycles, and these modules are just as easy to treat
like normal vendored code, then I could see us disabling the coupling.
Given the number of people who are currently doing coordinated changes with
major bustage across the API boundary in the two codebases today, I do not
see us turning this off in the near future. Unless, of course, things go
horribly awry with the infra or process in a way that puts Firefox at risk,
in which case all bets are off :-)
- Lars
On Tue, Jun 20, 2017 at 4:17 AM, Anthony Ramine wrote:
> In the future, will we try to uncouple servo from mozilla-central? I
> understand that it is needed now, but I don't see how such coupling is a
> good thing on the long term.
>
> Le 19 juin 2017 à 21:25, Jack Moffitt a écrit :
>
> Thank for everyone's efforts here. There never seems to be a perfect
> solution in technology, but I am happy we've found a solution that
> satisfies most of the constraints and were able to deploy it in time.
>
>
>
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
