post release change (previous*) #232
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
|
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 w3c/picture-in-picture#176 (comment) for an example.) |
|
Thank you for suggestions and guidance. Then, let me have them in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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)
💥 Error: 500 Internal Server Error 💥
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:
🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.
🔗 Related URL
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.