Re: [navigation-timing-tests] Update tools to include manifest v4 and csswg-test support (#4380)

>From IRC:

```
15:16 < gsnedders> Ms2ger, jgraham, MikeSmith: https://github.com/w3c/web-platform-tests/pull/4380 
                   — what are we waiting on? not being in the holidays?
15:16 < Ms2ger> Noticing it
15:17 < Ms2ger> I'm somewhat nervous about the question if wptupdate will keep working
15:35 < MikeSmith> I did not reply on that because I have nothing to add
15:46 < gsnedders> Ms2ger: surely we just have to face that at some point? :P
15:47 < Ms2ger> Sure, preferably at some point where jgraham can pick up  the pieces :)
15:47 < Ms2ger> OTOH, I just updated wpt in servo, so *shrug*
15:47 < gsnedders> is it run automatically such that it'd be a problem?
15:51 < gsnedders> we really need some agreement as to how to do breaking manifest changes
15:51 < gsnedders> and whether we consider introducing new test types to be a breaking change as 
                   well, I guess
```

I'd *really* like this landed before the CSS WG F2F starts on the 11th to try and get a resolution to do the actual merge soon thereafter.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/4380#issuecomment-269651706

Received on Thursday, 29 December 2016 16:06:48 UTC