- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Mar 2017 13:23:39 +0000
- To: public-secondscreen@w3.org
We're now at zero bugs blocking the revised CR publication. Congratulations!
@mfoltzgoogle, could you check that https://w3c.github.io/presentation-api/#changes-since-14-july-2016 is up to date? We're missing at least #414.
@mfoltzgoogle, is the "at risk" data provided at https://github.com/w3c/presentation-api/issues/406#issuecomment-279795674 still accurate?
@schien, do you see features in the spec you are not planning to implement (thus could be "at risk")?
("At risk" features are [formally][1] defined as "features [that] may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.")
@tidoust, do you see any blockers for advancing with the publication after we've updated changes since and added possible "at risk" features? Since the `allow-presentation` integration into HTML has not happen yet (tracked in https://github.com/w3c/html/issues/437) I suggest we go to revised CR with this token defined in https://w3c.github.io/presentation-api/#sandboxing-and-the-allow-presentation-keyword rather than block on HTML (the HTML integration issue has been open for ~10 months).
[1]: https://www.w3.org/2017/Process-20170301/#candidate-rec
--
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/406#issuecomment-288396433 using your GitHub account
Received on Wednesday, 22 March 2017 13:23:45 UTC