forked from servo/servo
-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2015 01 26
Josh Matthews edited this page Jan 26, 2015
·
1 revision
- Setting up CI for our dependencies? (larsberg)
- Finishing the rustup (https://critic.hoppipolla.co.uk/r/3832)
- Next rustup (slice changes, orphan impl check)
- jdm, kmc, Manishearth, Ms2ger, zwarich, mbrubeck, SimonSapin
Please put ideas for NCSU/GSoC projects here: https://etherpad.mozilla.org/servo-ncsu (deadline Feb 7), https://etherpad.mozilla.org/servo-gsoc (deadline Feb 20)
- manish: I might be able to set this up this week. Not sure how many of them have unit tests.
- kmc: Some our crates have unit tests; others might not. html5ever has a test suite that's in Travis already. rust-cssparser has something but I don't know the details.
- jdm: Will this be useful for crates that aren't tracking Rust master?
- kmc: Works for h5e/cssparser because it keeps updated regularly. Could do custom setup with snapshot.
- manish: I think we should track master. Or set up two different branches with different testing setups.
- kmc: Would be helpful when coordinating upgrades as a dashboard for which deps are upgraded.
- manish: Travis also shows when breaking upgrade occurs.
- kmc: If Servo is only user of many deps, not sure of value. For ones we want to promote to larger audience there's value, but otherwise it's a lot of extra work. What would be the ones to set up first?
- manish: string-cache, perhaps.
- kmc: string-cache isn't on travis yet. That's probably the next priority. I think there are people interested in using the mozjs/spidermonkey bindings, but that would be one of the hardest to keep updated.
- jdm: We have a pull request. Everyone please dive in and review what you can review. I'm on London time, so if someone in a later timezone wants to tag-team on addressing review comments, you can take over when I go to sleep.
- kmc: Niko blogged about the impl check changes.
- Manishearth: The old_orphan_check feature is still around, so we can just throw that everywhere to begin with and then start cleaning it up individually. Getting rid of it completely may require a lot of refactoring.
- Don't land anything until after the rustup lands.