chore(profiles/w3c-common): freeze profile to v25.5.0 #2838
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
sidvishnoi
requested review from
marcoscaceres,
samuelweiler and
saschanaz
and removed request for
samuelweiler
marcoscaceres
approved these changes
Apr 15, 2020
saschanaz
approved these changes
Apr 15, 2020
|
Maybe we should revisit https://github.com/w3c/respec/pull/2702 |
This was referenced Apr 15, 2020
9 tasks
xfq
referenced
this pull request
in w3c/jlreq
Jul 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/ltli
Jul 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/miniapp
Jul 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/simple-ruby
Jul 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/string-meta
Jul 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in xfq/mongolian-gb
Jul 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/klreq
Aug 16, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/i18n-activity
Aug 17, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/hlreq
Aug 20, 2020
The w3c-common profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/alreq
Aug 22, 2020
The w3c-common profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
xfq
referenced
this pull request
in w3c/klreq
Aug 27, 2020
The `w3c-common` profile was no longer updated. See https://github.com/w3c/respec/pull/2838 for details.
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.
🚨 We would no longer be updating
w3c-commonprofile. 🚨The profile will continue to be hosted at https://www.w3.org/Tools/respec/respec-w3c-common
Why?
It exposes some of ReSpec's internals, so we can't safely make changes to our internal structure and move forward. A lot of legacy specs use those internals, so we can't just remove them.
The most recent incident which triggered this decision is the breaking of https://w3c.github.io/json-ld-syntax/, which makes use of local-linking portion of core/link-to-dfn. [json-ld-syntax] broke as it wanted to hook between end of local-linking and start of external-linking - which we do not expose anymore.
How can we extend ReSpec now?
Presently, there is no way to do it. Not breaking specs is our priority. We do have plans to provide extensibility in future.
If you've a use case that other specs can also use, consider opening an issue/sending a PR so everyone can benefit from it!
Want new features and bug fixes?
Use the
respec-w3cprofile. It is nearly 90KB (30KB gzip) smaller thanrespec-w3c-common.Most of specs need to simply replace:
https://www.w3.org/Tools/respec/respec-w3c-common with
https://www.w3.org/Tools/respec/respec-w3c
TODO:
expose-module,pub("end, *)". Blocked by https://github.com/w3c/respec/issues/2152