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

editorial: add CR exit criteria #42

Merged
merged 2 commits into from
Aug 15, 2017
Merged

editorial: add CR exit criteria #42

merged 2 commits into from
Aug 15, 2017

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Jul 24, 2017

  • Addresses the "must document how adequate implementation experience will be demonstrated" for CR.

Preview | Diff

@marcoscaceres
Copy link
Member Author

@ianbjacobs ping.

@marcoscaceres
Copy link
Member Author

This now matches what is in the Payment Request API's conformance section.

index.html Outdated
The working group will demonstrate implementation experience by
creating a <a href="https://w3c-test.org/payment-method-id/">test
suite</a> and having at least two independent implementations pass each
mandatory test (i.e., each test the corresponds to a MUST requirements
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mandatory test (i.e., each test the corresponds to a MUST requirements

requirement (without the s)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, will fix in the other spec too.

Copy link
Contributor

@ianbjacobs ianbjacobs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi all,

I would like to again request that this information be m moved out of the conformance section and into the status section of the document.

This information is not related to how user agents conform to the specification, but rather how W3C will demonstrate interop.

@marcoscaceres
Copy link
Member Author

Heh, I had it in tge SOtD, but moved it because PR API had it in the wrong place.

@marcoscaceres marcoscaceres merged commit c179da3 into gh-pages Aug 15, 2017
@marcoscaceres marcoscaceres deleted the advancement branch August 15, 2017 07:17
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

Successfully merging this pull request may close these issues.

3 participants