Skip to content

Meeting 2014 04 28

Jump to bottom
Josh Matthews edited this page Apr 29, 2014 · 1 revision

Servo Meeting 2014-04-28

Reminder

Please update your status at: http://benjamin.smedbergs.us/weekly-updates.fcgi/

Agenda

  • Introductions of new team member and intern and gsoc student!
  • rooting rebase
  • Rust upgrade - should we start another one immediately? And change submodule process at all?

Introductions

  • jack: Welcoming our new team members. Brendan (bjz) is joining as an intern, working on SIMD word wrapping. Glenn also is joining full-time, working on platform features.
  • jdm: As of Thursday, Manish will be starting his GSoC work on XMLHttpRequest. It is earlier than the usual google summer of code internships due to India's schedule.

Rooting rebase

  • jack: How is that going, jdm?
  • jdm: It's coming slowly. I'm halfway through the first commit, merging it with the Rust upgrade that just landed.
  • mbrubeck: Have we considered doing a merge instead of a rebase to help avoid resolving the same conflicts? It's harder to audit, though...
  • jack: Critic will show us the merge stuff fine.
  • mbrubeck: I mean for the person doing the rebase. The rebase with the replays on top of it, often mean you are re-fixing things over and over instead of a single time (for a merge).
  • jdm: For me, I like to make sure each rebase commit builds and passes tests. After that, it should be easier to bisect...
  • jack: Will you squash those minor edits, jdm?
  • jdm: Yes.
  • mbrubeck: git bisect can go along all branches of a merge (it's better than hg bisect).
  • jack: Should we hold changes until this lands?
  • jdm: Keep reviewing and landing changes.

Rust upgrade

  • larsberg: Should we start another one?
  • jack: What has broken?
  • jdm: Glob re-exports?
  • brson: Those are just gated.
  • jdm: We've fixed some of them, but still need it in script.
  • jack: "we enable all features of Rust" Do we lose ~[]?
  • brson: Yes, all push stuff has to be on Vec.
  • jdm: We already have PRs to fix them all.
  • jack: I'm fine with starting one. But not until after rooting lands.
  • pcwalton: And my stuff (parallel layout). Just need to fix a reftest.
  • jack: Ok, land jdm's rooting and pcwalton's parallel layout & displaylist rewrite. So start in a week and a half and hopefully it will be quick. brson, any breaking changes that would make this hard?
  • pcwalton: ~ might be gone...
  • brson: Not in a week and a half.
  • jack: We'll try to beat the ~ change in Rust master. But if we've already switched to Vec it may not be that bad...
  • pcwalton: layout. should be mechanical (just ~ to box).

Web platform tests

  • jack: did that land?
  • jdm: It failed to merge / pass the tests.
  • jack: What percentage do we pass currently?
  • jdm: I don't know.
  • jack: I'd be curious about how we relate to gecko.
  • pcwalton: How close are we to jquery?
  • jack: querySelector is the hard part...
  • jdm: None of the required work is layout.
  • pcwalton: If you use queryselector on the layout side....
  • jdm: There's a PR that uses the bits from the style crate, but no code from the layout directory/task.
  • pcwalton: Nice! I forgot that the style code is abstracted away.
  • jack: Where was CSSOM?
  • larsberg: We had it as a stretch goal for Q2: https://github.com/mozilla/servo/wiki/Roadmap
  • jack: Maybe ms2ger!

Plan for stable rust build

  • jack: Lars, do you want to talk about your plan for switching to the rustc binary snapshots?
  • lars: I wasn't planning to switch to the official Rust release downloads.
  • lars: What I wanted to do was create an s3 bucket for servo builds so that whenever servo decides on a rust build to use we package up a rust build to use (4 flavors). I may also need to create an arm cross target as well (non-android). Brian has a bunch of scripts that it looks like I can reuse. Unless people really like compiling rust themselves, I plan on doing this really soon.
  • jack: How does Rust bootstrapping know which URL to get?
  • brson: We have a big text file in the repo with the IDs of every snapshot ever created, which are in a format that can be converted to a URL where the snapshot can be downloaded.
  • lars: We can't just reuse the snapshots that the Rust team uses, because we need more flavors than they do.
  • brson: it would be nice if we extended the Rust build system to include the new targets, so your build system just becomes our build system. You may be able to adapt the nightly code.
  • jack: I like this plan. Not having to build Rust to build servo will be a huge win. It will also, if it has more builds available, we can bisect to find Rust bugs more quickly.
Clone this wiki locally