Next release will be 0.1.0, not 1.0.0
Since synapse is already doing the new behavior on r0 endpoints, and nobody wants to support the old behaviour, we're defining the new behaviour as r0.1.
This commit is contained in:
parent
8f4d7c95df
commit
590c55b760
1 changed files with 8 additions and 2 deletions
|
@ -1,9 +1,9 @@
|
|||
r1.0.0
|
||||
r0.1.0
|
||||
======
|
||||
|
||||
This release includes the following changes since r0.0.1:
|
||||
|
||||
- Breaking changes to the API:
|
||||
- Breaking changes to the API [#]_:
|
||||
|
||||
- ``POST /rooms/{roomId}/join`` no longer permits use of a room alias instead
|
||||
of a room id. (``POST /join/{roomIdOrAlias}`` continues to allow either.)
|
||||
|
@ -56,6 +56,12 @@ This release includes the following changes since r0.0.1:
|
|||
``PUT /pushers/set``, and note that it is not mandatory.
|
||||
|
||||
|
||||
.. [#] Our `versioning policy <../index.html#specification-versions>`_ would
|
||||
strictly require that a breaking change be denoted by a new major
|
||||
specification version. However we are not aware of any clients which
|
||||
rely on the old behaviour here, nor server implementations which offer
|
||||
it, so we have chosen to retain the r0 designation on this occasion.
|
||||
|
||||
r0.0.1
|
||||
======
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue