Le 08/02/2017 à 12:39, Simon Sapin a écrit :
So here is a proposal to avoid this situation in the future:
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.
There is a solution for this sort of problem in the npm ecosystem :
https://greenkeeper.io/
It's a bot that you hook into your project. It finds the dependencies
and whenever the dependency releases a new version, greenkeeper sends a
Pull Request like this one : https://github.com/sudweb/2015/pull/84
With CI, all the tests are run instantly so you know whether using the
new dependency will break something.
It only works on npm packages/repos, but it doesn't seem shockingly hard
to copy the design and apply to rust crates/repos.
This could be a solution to the problem "there is a new dependency
version, let's open a PR about it" and "and 39 crate publishes, each of
which requires futzing around with Cargo dependencies". The bot would be
doing all this.
David
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
