From 33f4171144e350e6eb06cbf47183ce532ca7c44f Mon Sep 17 00:00:00 2001
From: Marcos Caceres
Date: Wed, 3 May 2017 15:00:32 +1000
Subject: [PATCH 1/2] editorial: document mandatory things needed for cr
* Provides a link to a label on GitHub's issue tracker for public documentation of all substantive changes since previous publication.
* Provides a link to all commits as public documentation of changes that are not substantive.
* Documents that the dependencies during the development of the specification have not changed.
* Document how adequate implementation experience will be demonstrated (shipping implementations + test suite)
* Specifies 31 December 2017 as the deadline for CR comments.
---
index.html | 43 +++++++++++++++++++++++++++++++++++++++----
1 file changed, 39 insertions(+), 4 deletions(-)
diff --git a/index.html b/index.html
index 571abe9c..ac37a1f8 100644
--- a/index.html
+++ b/index.html
@@ -48,6 +48,12 @@
issueBase: "https://github.com/w3c/browser-payment-api/issues/",
otherLinks: [{
+ key: "Can I use this API?",
+ data: [{
+ value: "caniuse.com",
+ href: "http://caniuse.com/#feat=payment-request",
+ }],
+ },{
key: "Version control",
data: [{
value: "Github Repository",
@@ -55,7 +61,13 @@
}, {
value: "Issues",
href: "https://github.com/w3c/browser-payment-api/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20-label%3A%22Priority%3A%20Postponed%22%20"
- }]
+ }, {
+ value: "Substantive changes from FPWD to CR",
+ href: "https://github.com/w3c/browser-payment-api/pulls?q=is%3Apr+is%3Aclosed+label%3Acr-substantive",
+ },{
+ value: "Commit history",
+ href: "https://github.com/w3c/browser-payment-api/commits/gh-pages",
+ },]
}]
};
@@ -86,9 +98,8 @@
are strongly encouraged.
- This specification was derived from a report published previously by
- the Web Platform Incubator
- Community Group.
+ The deadline for comments for Candidate Recommendation is 31 December
+ 2017.
@@ -2864,7 +2875,31 @@
way desired, so long as the end result is indistinguishable from the
result that would be obtained by the specification's algorithms.
+
+ The working group will demonstrate implementation experience by
+ creating a
+ test suite and having at least two independent implementations pass
+ each mandatory test (i.e., each test the corresponds to a MUST
+ requirements of the specification). The working group hopes to
+ demonstrate, in the form of an implementation report, interoperability
+ from two or more vendors on both mobile and desktop web browsers.
+
+
+ There has been no change in dependencies on other workings groups
+ during the development of this specification.
+
+