Skip to content
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

Closed
4 of 6 tasks
anssiko opened this issue May 18, 2017 · 12 comments
Closed
4 of 6 tasks

[meta] Publish a revised Candidate Recommendation #12

anssiko opened this issue May 18, 2017 · 12 comments
Assignees

Comments

@anssiko
Copy link
Member

anssiko commented May 18, 2017

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:

  • must show that the revised specification meets all Working Group requirements, or explain why the requirements have changed or been deferred,
  • must specify the deadline for further comments, which must be at least four weeks after publication, and should be longer for complex documents,
  • must document the changes since the previous Candidate Recommendation,
  • must show that the proposed changes have received wide review, and
  • may identify features in the document as "at risk". These features may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.

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.

@anssiko anssiko self-assigned this May 18, 2017
@dontcallmedom
Copy link
Member

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.

@anssiko
Copy link
Member Author

anssiko commented May 22, 2017

@Honry and @riju, can you provide updated test results?

@anssiko
Copy link
Member Author

anssiko commented May 22, 2017

@fhirsch @dontcallmedom, the proposed text for changes since: bf3b86b

Does it look good to you?

@Honry
Copy link
Contributor

Honry commented May 23, 2017

@anssiko, the CL is still under review, @riju is testing on Chrome on Linux and Mac, shell we also include test results on these two platforms?

@anssiko
Copy link
Member Author

anssiko commented May 23, 2017

@Honry, yes, please include the test results on these two new platforms, in addition to Android.

@Honry
Copy link
Contributor

Honry commented May 23, 2017

Sure, I am waiting for @riju's results or the CL being landed.

@anssiko
Copy link
Member Author

anssiko commented Jun 1, 2017

@Honry, the changes have landed, see https://codereview.chromium.org/2880763002/

@Honry
Copy link
Contributor

Honry commented Jun 2, 2017

OK, I will deliver a refreshed test report soon.

@Honry
Copy link
Contributor

Honry commented Jun 12, 2017

@anssiko, I just committed the updated test result at w3c/test-results#101, PTAL.

@anssiko
Copy link
Member Author

anssiko commented Jun 15, 2017

Reopened #10 pushing back the revised CR publication.

@xfq
Copy link
Member

xfq commented May 27, 2021

I guess we can close this now, per https://lists.w3.org/Archives/Public/public-device-apis/2021May/0012.html

@anssiko
Copy link
Member Author

anssiko commented May 27, 2021

We resolved to publish a new Working Draft, so we can close this meta issue.

@anssiko anssiko closed this as completed May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants