Skip to content
Brian Anderson edited this page May 20, 2013 · 2 revisions

Agenda

  • release engineering
  • interns
  • hiring

Attending

brson, pcwalton, jack, azita, tkuehn, eatkinson

release engineering

  • jack: we have continuous integration on servo. bors has integrated two patches
  • patrick: process is same for rust?
  • jack: pull request gets made for servo, somebody reviews it, adds comments if the review is negative. if the review is positive they add 'r+' to the commit. then bors will go run the tests on the branch and merge it into the tree. it won't merge if any tests fail.
  • jack: on rust this works great and you see on #rust that bors is constantly merging patches
  • jack: we haven't had this on servo, lots of problems with the build process.
  • jack: so now we have 'bors' on servo, running only linux, but os x should follow in a few days
  • jack: the only thing missing from bors is we don't have access to the build logs or the pull request queue
  • brson: no bors status page?
  • jack: not yet, and we don't have access to the machines either
  • jack: those are the three things we still have to do.
  • patrick: it doesn't tell you what fails?
  • jack: probably generates a link that goes nowhere
  • brian: strange that firefox's logs aren't public
  • jack: we'll get them, should have it working in a few days
  • jack: it sounds like we'll have to talk to ben's bosses about scheduling the android build, windows builds, etc.
  • jack: right now we don't have independent dependency management
  • patrick: so bors does not manage the submodules
  • jack: are you (interns) familiar with github?

interns

  • jack: did you get to talk about projects at lunch?
  • tim: a little
  • patrick: briefly. is seth here?
  • jack: nope
  • patrick: erick has expressed interest in layout and there's a done to be done. should coordinate with seth since he's working on the same stuff. do you know the status of his border patches?
  • jack: two things under warmup are 'support all units' and borders.
  • patrick: units are done
  • brson: I don't think so
- jack: easiest place is margins, padding, floats. - patrick: I know seth has changed some stuff here - brson: out of tree? - patrick: yes - brson: it's going to take erick some time to get up to speed - patrick: thinking tim could port servo to new scheduler. maybe not best first thing - brson: pick something smaller scope - jack: maybe a first thing to do is learn rust. if you're feeling adventurous work on brian's io branch - brson: it's all upstream for the moment - patrick: trying to think of things that need doing that are not - brson: the best intro problems will involve touching lots of servo while writing rust - patrick: are text transforms working? making text uppercase lowercase. might be fun - jack: friday we were talking about timing the compositor. adding timing in various places - patrick: better timing infrastructure, not a hard project but could be involved - patrick: another possibility is fixing regressions in real pages - brson: we don't have the test infrastructure - patrick: compare performance against gecko on display list building, etc. - jack: also useful when we want to build more performance infrastructure to know how gecko does it.
Clone this wiki locally