[w3c/browser-payment-api] CR check list (#520)

For all Transition Requests, to advance a specification to a new maturity level other than Note, the Working Group:

* [ ] must record the group's decision to request advancement.
* [ ] must obtain Director approval.
* [ ] must provide public documentation of all substantive changes to the technical report since the previous publication.
* [ ] must formally address all issues raised about the document since the previous maturity level.
* [ ] must provide public documentation of any Formal Objections.
* [ ] should provide public documentation of changes that are not substantive.
* [ ] should report which, if any, of the Working Group's requirements for this document have changed since the previous step.
* [ ] should report any changes in dependencies with other groups.
* [ ] should provide information about implementations known to the Working Group.

To publish a Candidate recommendation, in addition to meeting the general requirements for advancement a Working Group:

 * [ ] must show that the specification has met all Working Group requirements, or explain why the requirements have changed or been deferred,
 * [ ] must document changes to dependencies during the development of the specification,
 * [ ] must document how adequate implementation experience will be demonstrated,
 * [ ] must specify the deadline for comments, which must be at least four weeks after publication, and should be longer for complex documents,
 * [ ] must show that the specification has 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.
 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/520