Let's allow until Friday afternoon for feedback to come in, but I don't think it makes sense to delay this decision.
jack. On Wed, Feb 8, 2017 at 12:23 PM, Simon Sapin <simon.sa...@exyr.org> wrote: > On 08/02/17 19:42, Bobby Holley wrote: >> >> Won't they need to do this anyway? At least assuming we accept your >> proposal below that: "Whenever a PR to rust-selectors (and other >> repositories where we think that’s appropriate) makes breaking changes, we >> don’t land it until there’s also a corresponding PR to update Servo for >> these changes." > > > No. If a contributor makes a change that is breaking, I or someone else on > the Servo team would take care of updating Servo for them. > > >> We have two years of historical data. That does not predict the future, >> it's at least some indication of the volume we might expect in the near >> term. > > > I agree with your cost / benefit analysis. But as I mentioned before, my > reluctance is also based on principle. > > >> But please consider that it causes me (and some others) a lot of pain. > > > I believe you, but to be honest I don’t understand. (To me, contributing to > Gecko also requires jumping through a number of (different) hoops.) > > > I’m inclined to concede, but I’d like to hear from other people before > hitting the button. > > > -- > Simon Sapin > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
