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

chore: auto-publish spec as WD #119

Merged
merged 2 commits into from
Jun 7, 2021
Merged

chore: auto-publish spec as WD #119

merged 2 commits into from
Jun 7, 2021

Conversation

marcoscaceres
Copy link
Member

No description provided.

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

@marcoscaceres
Copy link
Member Author

Great! we plan to give this treatment 💅 to the rest of the specs... do you have a preference for which specs we should prioritize? Could you let us know in w3c/web-performance#34? Otherwise, we will just work our way down the list there.

@marcoscaceres marcoscaceres merged commit 853843c into gh-pages Jun 7, 2021
@marcoscaceres marcoscaceres deleted the auto-publish branch June 7, 2021 06:36
@yoavweiss
Copy link
Contributor

Resource Timing and Performance Timeline would be nice to tackle next, as they also have external reliance and would be good to clean up. Thanks!! :)

@caribouW3
Copy link
Member

The problem will be that those specs are stuck in their CR transitions. We should definitely auto-publish once they're in CR.

@marcoscaceres
Copy link
Member Author

@caribouW3, could we still set them up? If we need to get wide review again for those specs before we can progress them, then we could still just auto-publish them as they are now. After they go to CR, all we need to do is just change the auto-pub file to use "CRD". See, for example, w3c/payment-request#959

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.

3 participants