W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2017

Transiting to CR - issues we need to resolve

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 22 Jun 2017 11:41:19 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <VI1PR0701MB2733E0A839F01BD00E9B112DC9DB0@VI1PR0701MB2733.eurprd07.prod.outlook.com>
All,

we have now had the reviews come in (and thanks everyone for reviewing!), and Issues have been filed as result of that [1].

We have gone through them, and our assessment is that only a sub set of them must be resolved before requesting transition to CR (remember that a CR is issued to signal to the wider community that it is time to do a final review and to gather implementation experience etc. [2]).

There are 8 Issues labeled "Resolve before CR" [3] and we think that once those are resolved we can request the transition to CR (the remaining Issues must of course be resolved before transiting to PR). Our plan is to deal with them (and ideally resolve them) at the upcoming June 28 VI. 

Please help enabling that by reading up (and ideally take part in the discussion in the issues) before the meeting. Note that many of them will likely be resolved without any changes to the spec (i.e. we do not need PRs for all of them).

And let us know if you think there are other things we must resolve before CR transition.

Bernard and Stefan


[1] https://github.com/w3c/webrtc-pc/issues

[2] https://www.w3.org/2017/Process-20170301/#maturity-levels

[3] https://github.com/w3c/webrtc-pc/labels/Resolve%20before%20CR
Received on Thursday, 22 June 2017 11:41:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC