Does this also mean servo is going to move off of homu, and lose pre-commit testing? How is the contributor experience going to be impacted by the change?
On Mon, Jun 20, 2016 at 8:01 AM, Lars Bergstrom <larsb...@mozilla.com> wrote: > As many of you may have seen from the document > ( > https://docs.google.com/document/d/1uubYE7JXaVY10PoAY9BVx8A-T11ZxP1RYqNOrFJwdcU/edit > ) > and discussions on dev-build and at the workweek, we have an > increasing desire to be able to try to develop and potentially ship > Servo code in Firefox. While this is exciting (yay, customers! yay, > faster Firefox!), it also means that we're going to be subject to some > growing pains as we around the requirements of our largest and best > customer. > > We'd like to hear your comments here (or privately, if you prefer) > about these proposed changes. We're trying to figure out all of the > details, so now is the right time to bring up objections or > requirements! > > 1) Move our CI testing for servo/servo off of buildbot and into releng. > > In order to ensure Servo changes do not break Firefox and vice-versa, > we are proposing unifying our autolanders and moving Servo's tests (as > Tier 1 - must pass to commit!) into releng. This would also mean > running relevant Firefox tests against Servo. > > 2) Move webrender and webrender_traits back into the Servo repository. > > Because WebRender and Stylo are the two biggest projects that will > need to be worked on in a cross-cutting way across Firefox and Servo, > we'd like to have them out of a separate GitHub repo (with its "update > version, PR, cargo publish, pull down, repeat" workflow) and in the > one that is being tested and co-landed with Firefox. We plan to push > webrender to crates.io to ensure it is still separately usable by > other projects. > > 3) Get Stylo and WebRender onto stable Rust. > > It is the intention to ship Rust code in Firefox using only stable > Rust features. That's not a hard requirement, but it means trying to > either stabilize features or rip out any unstable/nightly-only > features in use in either the Stylo or WebRender dependency graphs. > > Please provide feedback on these topics or any others that come to > mind around these changes! Many of us across the company will be > working hard in the coming weeks to get a concrete proposal and > timelines in place for this work, so please reach out with your > concerns ASAP. > > Thanks! > - Lars > _______________________________________________ > 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
