You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
matrix-spec-proposals/content
Andrew Morgan fca6992cd9 Clarify that implementations can use stable prefixes once an MSC has merged (#3179)
Fixes #3146.

This PR changes the Matrix Spec Proposals page to clarify that implementations **do not** need to wait until a spec release to use stable prefixes, but that they can do so after the corresponding MSC has been merged. The justification is that once an MSC has been merged, it's fairly guaranteed that it will land in the spec. Yet it will take time for the spec release process to run its course, and we shouldn't make implementations wait for that.

The exception to this is if implementating a feature in a backwards-compatible way requires a new spec version to indicate to clients/servers that a feature has been added/changed. This situation is rare though, and most implementations won't fall into this category.
3 years ago
..
client-server-api Merge pull request #3170 from matrix-org/travis/spec/msc2713-rm-v1-id 3 years ago
rooms Add knocking to the spec 3 years ago
_index.md Add knocking to the spec 3 years ago
appendices.md Remove group identifiers 3 years ago
application-service-api.md Update content to call the new template for HTTP APIs 3 years ago
changelog.md Add changelog page and templates 4 years ago
identity-service-api.md Merge pull request #3170 from matrix-org/travis/spec/msc2713-rm-v1-id 3 years ago
proposals.md Clarify that implementations can use stable prefixes once an MSC has merged (#3179) 3 years ago
push-gateway-api.md Update content to call the new template for HTTP APIs 3 years ago
server-server-api.md Add knocking to the spec 3 years ago