Our stylo workflow thus far has required a brave soul (usually heycam or Manishearth) to periodically merge updates from mozilla-central and servo/servo into incubator. We are now in a place where we can (hopefully) remove this step.
Some new developments: * As of last week, mozilla-central has a copy of servo/servo in the top-level servo/ directory. * As of yesterday, new PRs that land on servo/servo get automatically landed to integration/autoland, which the sheriffs regularly merge to and from mozilla-central. * Manish is currently working on |cargo vendor|-ing geckolib's dependencies into mozilla-central. Once this is done, we should be able to turn on linux64-stylo jobs on autoland, inbound, and mozilla-central. So I'd like to try retiring incubator and switching to mozilla-central for stylo development. If it doesn't work, we'll learn something, and can fall right back to incubator until we're ready to try again. The servo/ directory is read-only except for the sync bot, and we're still some time from being able to modify it and have the autolander mirror the changes to servo/servo. This means that servo-side changes still need to land on servo/servo. If there are interdependent gecko changes, the servo-side changes should land first. Once they hit autoland, the developer should promptly land the gecko-side changes to minimize the interval of bustage. This also means that we now have shorter cycle times between the introduction and the detection of bustage. If your patch breaks something, please fix it immediately to keep autoland green. In summary, here's the new workflow - I'll send out another email when the jobs are running and we can start using it: (1) New stylo-related changes should land on autoland and servo/servo. (2) Developers should use mozilla-central for local development. Comments and discussion welcome. Thanks for everyone's work on this! bholley _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
