[heycam/webidl] Improvements to downstream tracking (#379)

We experimented with being much more thorough and organized at filing bugs downstream, notifying browser vendors, WebIDL parsers, idlharness, wpt and affected specs.

Overall, I'm super pleased with the outcome of the outreach. It's great to see changes in the spec being adopted so quickly downstream. It's also really nice to get feedback and questions from editors on how they're handling the changes. Ultimately, I hope this also makes WebIDL more approachable and helps build a tighter community around spec editing.

Unfortunately, this increased velocity has also caused some casualties, notably within the perf WG, which so a number of its ED drafts no longer render when ReSpec was updated (see the thread on this topic here: https://github.com/w3c/resource-timing/issues/112).

Although this is essentially a ReSpec issue, it would be nice to see how we can avoid that in the future and if there are other improvements that can be made here.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/379