VTT, moving along, push WD and review Wide Review

Friends

the CG has worked in email and GitHub to close out all the issues that were revealed in the previous wide review, and believes that those, and other critical issues, have been handled. I have asked the CG for confirmation of this.

On the page <https://www.w3.org/wiki/WebVTT_Wide_Review>  you will find documentation of the wide review received. It was built in the days when we were using BugZilla, so alas, for bugs that were transferred to GitHub and resolved there, you’ll need to follow forwarding pointers, to see the complete history (if you care).

Thierry would like a formal status from the WG on each bug; you’ll see the table of possible statuses at the end of the page (has this been done for other specs?). I have not yet filled in the WG column, but obviously could take the implied status from the CG column. Please let the group know if you think that is wrong.

The specification is in much better shape; the test suite has been greatly improved (we hired a contractor) and does good coverage. We are working on a test report. With that in hand, we are hoping for a quick wide-review prior to a CR transition. Yes, we expect that some features will be marked ‘at risk’ in that transition; we’ll be looking at the test report.

The latest editor’s draft is at <https://w3c.github.io/webvtt/>. I think we are badly behind on the working draft heartbeat requirement; I would like to push this as a WD. We previously asked for assent to have the editor push WDs automatically, but the WG indicated it preferred a resolution. Please consider resolving this in email or on a call (as you prefer). I cannot join the call this week.

Once we have:
* your acceptance of the handling of the wide review issues
* the WD in place
* the test suite report in hand

I expect to ask for a transition to CR.

Thank you for your patience and attention; it has been a long road.



David Singer
Manager, Software Standards, Apple Inc.

Received on Wednesday, 28 June 2017 10:18:39 UTC