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

How to deal with versioned specs #2

Open
gsnedders opened this issue Mar 30, 2017 · 2 comments
Open

How to deal with versioned specs #2

gsnedders opened this issue Mar 30, 2017 · 2 comments

Comments

@gsnedders
Copy link
Member

e.g., the CSS WG has both css-cascade-3 and css-cascade-4 on the REC-track at different stages; how should the WG deal with testing these given the general policy of wpt being unversioned?

@fantasai
Copy link

This is why we tag things with spec links. I don't understand your concern.

@gsnedders
Copy link
Member Author

@fantasai The CSS WG does, yes. But an introductory document for testing across the W3C as a whole should give pointers to solutions and how they interact with tooling available for preparing implementation reports.

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

No branches or pull requests

3 participants
@gsnedders @fantasai and others