wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Answer question about confusing deprecation with not

Browse source
This commit is contained in:
Travis Ralston 2020-11-12 17:51:22 -07:00
parent 1310c7c8bf
commit d079d7d2d3
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
proposals/2844-global-versioning.md
View file

@ -226,6 +226,13 @@ in favour of its proposed `/v4/sync`. Because endpoints are versioned on a per-e
will still work with a server that supports `/v3/profile` (for example) - the version number doesn't mean will still work with a server that supports `/v3/profile` (for example) - the version number doesn't mean
an implementation can only use v4 endpoints. an implementation can only use v4 endpoints.
This sort of approach could be potentially confusing and non-standard as it would mean for an amount of
time in the specification there would be two versions of an endpoint: one deprecated and one not. Most
specifications and protocols do not use this sort of approach and instead opt to replace the whole API
or outright remove the endpoint, however the Matrix specification tends to have a longer-lived cycle
associated with it and thus means we should support a larger than average backwards compatibility
period.
### Supported versions schedule ### Supported versions schedule
Currently implementations are left to fend for themselves on deciding which versions of their APIs to Currently implementations are left to fend for themselves on deciding which versions of their APIs to