Closed himorin closed 4 years ago
Why do we need to uncomment these lines in the ED?
Ah,, looking to others, I thought these are required lines even for ED.... e.g. https://drafts.csswg.org/web-animations-1/ https://immersive-web.github.io/webxr-ar-module/
I don't believe so. I left them commented out for the ED of the 25 or so documents i recently published.
I think different groups have different preferences on this. CSS specs always contain links to previous versions, while some groups do not. (See https://github.com/w3c/picture-in-picture/pull/176#discussion_r374039950 for an example.)
Thank you for suggestions and guidance. Then, let me have them in ECHIDNA
but not in the spec.
Adding previousPublishDate and previousMaturity as https://www.w3.org/TR/2020/NOTE-jlreq-20200811/
(do we want to tag the released one with the real configurations?? - if so, we need to do before merging this PR)
:boom: Error: 500 Internal Server Error :boom:
PR Preview failed to build. (Last tried on Aug 11, 2020, 5:52 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one: :rotating_light: [Spec Generator](https://www.w3.org/2015/labs/) - Spec Generator is the web service used to build specs that rely on ReSpec. :link: [Related URL](https://labs.w3.org/spec-generator/?type=respec&url=https%3A%2F%2Frawcdn.githack.com%2Fhimorin%2Fjlreq%2Fb8a1c846b6cfebfee48791cf8352a38f5954e68e%2Findex.html%3FisPreview%3Dtrue) ``` Navigation timeout of 30000 ms exceeded ``` _If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please [file an issue](https://github.com/tobie/pr-preview/issues/new?title=Error%20not%20surfaced%20properly&body=See%20w3c/jlreq%23232.)._