-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[meta] Publish a revised Candidate Recommendation #12
Comments
re wide review, I think it would be good to point WebAppSec to the proposed changes and ask for feedback. But that's about the only group that I can think of in this case. |
@fhirsch @dontcallmedom, the proposed text for changes since: bf3b86b Does it look good to you? |
@Honry, yes, please include the test results on these two new platforms, in addition to Android. |
Sure, I am waiting for @riju's results or the CL being landed. |
@Honry, the changes have landed, see https://codereview.chromium.org/2880763002/ |
OK, I will deliver a refreshed test report soon. |
@anssiko, I just committed the updated test result at w3c/test-results#101, PTAL. |
Reopened #10 pushing back the revised CR publication. |
I guess we can close this now, per https://lists.w3.org/Archives/Public/public-device-apis/2021May/0012.html |
We resolved to publish a new Working Draft, so we can close this meta issue. |
On today's call we decided to publish a revised Candidate Recommendation.
I've staged a snapshot (work in progress):
Per the process for revising a CR, the group needs to address the following requirements:
Other
@fhirsch @dontcallmedom, am I right in assuming we do not need a new wide review? I took an action to document the changes since the previous Candidate Recommendation to tick the last remaining box, after which @fhirsch you could issue a CfC to publish.
The text was updated successfully, but these errors were encountered: