Dear WPWG, At last week’s meeting [1] we set an expectation that we would log issues for Payment Request API and Payment Handler API for 6 April discussion. In more detail: * Is possible, please log your issues by 4 April, so that the Editors may review and collate them for an efficient 6 April discussion [2]. Here are links to the relevant issues lists: PR API: https://github.com/w3c/browser-payment-api/issues Payment Method Identifiers (PMI): https://github.com/w3c/webpayments-method-identifiers/issues Basic Card: https://github.com/w3c/webpayments-methods-card/issues Payment Handler API: https://github.com/w3c/webpayments-payment-apps-api/issues * On 6 April we will try to freeze the issues in the following sense: - For PR API and PMI, this will be the list that we endeavor to address before the Chairs issue a call for consensus to enter CR. If we cannot address them, we may also make a decision to postpone them to another version of the specs. - For Payment Handler API, this will be the list that we try to address before FPWD OR simply mark as open in the FPWD (as we have done for previous specifications). This is likely to require less time than PR API, and therefore the call for consensus for Payment Handler to go to FPWD may arrive sooner. I am working with the Chairs on a more detailed plan for getting to CR that I will send to the group before next week’s call. Ian [1] https://www.w3.org/2017/03/24-wpwg-minutes#item05 [2] https://github.com/w3c/webpayments/wiki/Agenda-20170406 -- Ian Jacobs <ij@w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447Received on Friday, 31 March 2017 14:10:45 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:24 UTC