docs-matrix-spec/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.
2021-08-27 19:17:14 +01:00
..
client-server-api Merge pull request #3170 from matrix-org/travis/spec/msc2713-rm-v1-id 2021-08-27 19:17:13 +01:00
rooms Add knocking to the spec 2021-08-27 19:17:12 +01:00
_index.md Add knocking to the spec 2021-08-27 19:17:12 +01:00
appendices.md Remove group identifiers 2021-08-27 19:17:13 +01:00
application-service-api.md Update content to call the new template for HTTP APIs 2021-08-27 19:16:42 +01:00
changelog.md Add changelog page and templates 2021-02-02 20:47:18 -08:00
identity-service-api.md Merge pull request #3170 from matrix-org/travis/spec/msc2713-rm-v1-id 2021-08-27 19:17:13 +01:00
proposals.md Clarify that implementations can use stable prefixes once an MSC has merged (#3179) 2021-08-27 19:17:14 +01:00
push-gateway-api.md Update content to call the new template for HTTP APIs 2021-08-27 19:16:42 +01:00
server-server-api.md Add knocking to the spec 2021-08-27 19:17:12 +01:00