Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update process #80

Merged
merged 4 commits into from Aug 3, 2022
Merged

Update process #80

merged 4 commits into from Aug 3, 2022

Conversation

clelland
Copy link
Contributor

@clelland clelland commented Aug 2, 2022

This updates the ReSpec version used to conform to Process 2020

New ReSpec metadata errors introduced by this are addressed as well.


Preview | Diff

@clelland clelland requested a review from yoavweiss August 2, 2022 15:39
Copy link
Contributor

@yoavweiss yoavweiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yoavweiss
Copy link
Contributor

Seems like the bots fail on respec errors. Can you take a look?

@clelland
Copy link
Contributor Author

clelland commented Aug 2, 2022

There are two errors, caused by the override in the build config that sets the document to CRD status:

  • There's no CR end date (this is a "no-earlier-than" date for advancement, so I could just set that to 2022-08-01 and be done with it)
  • There's no "implementation report", which appears to be required for CR and CRD status. Do we have something like that for Beacon? (I don't expect that linking to wpt.fyi is sufficient here, but CSP's doesn't look too far off of that)

@clelland
Copy link
Contributor Author

clelland commented Aug 2, 2022

NM, I missed both of those bullet points. They're both specified already in https://www.w3.org/TR/beacon/.

@clelland clelland requested a review from yoavweiss August 3, 2022 02:37
@clelland clelland merged commit 7b6f20e into w3c:gh-pages Aug 3, 2022
@clelland clelland deleted the update-process branch August 3, 2022 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants