Philip Jägenstedt

There's also beta releases, which is mostly a matter of changing those dates. But once stable is released, we also need to check for contradictions in the results, in case...

@queengooborg can you add the "proposed for Q3 2022" label for this?

@teoli2003 how about you?

Oops, thanks and sorry for the noise!

What remains of the original checklist is "Vetting places where manual data remains and is likely to be wrong". @queengooborg do you have thoughts on how we should go about...

> Or to solve the question how to document `Response.prototype.json` and a static `Response.json` on MDN/BCD? This is the motivating case, to make it possible to document these at the...

I have no previous involvement with sourcemaps, maybe @mathiasbynens knows who might know?

I've seen something similar when triaging testharness.js subtests. Then, searching searches for the name of the subtest, which honestly is very unlikely to find a bug, and just searching by...

Constructing the diff URLs in https://github.com/web-platform-tests/wpt/issues/14495 was quite time-consuming, so automatically comparing all pairs of master runs for a configuration would help immensely.

Doing https://github.com/web-platform-tests/wpt/issues/13263 would mitigate the need for this somewhat, but I'd still love to have links to diffs for each master run, even if there aren't regressions.