-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Where are the room versions and their changelogs? #1043
Comments
https://spec.matrix.org/unstable/#complete-list-of-room-versions seems to be what you're looking for. It has room version 7 listed as "Stable" and I assume room version 8 will come "soon" now that the MSC has merged. |
Thank you, will the first link automatically point there or will all links need to be updated when the new spec is released? Is there a timeline for that somewhere? |
@Mikaela I am not sure what the final URL of the new spec redesign will be or how the redirects will be setup from the old spec. I think the new canonical spec home will be For a plan/timeline of the new spec redesign release, see matrix-org/matrix-spec-proposals#3095 |
@Mikaela is this issue still relevant or can it be closed? :) |
Yes, I think this has became clearer since then, thank you. |
I have a script for manually updating rooms where I advice people to check what is the current room version before using it. However the list on the website is missing room version 7 entirely while recent Synapse is already on version 8.
Where can I find room version 7, what changed with it and where will version 8 and future room versions be explained?
Finnish Matrix user group tells me that the docs/spec is no longer updated and the replacement isn't released yet (is this correct?), but can be previewed from /unstable/ which again doesn't have an equivalent page.
In addition to not telling me what has changed at a glance or whether the room version is stable, I am not sure if I should link production users to somewhere saying /unstable/ and
The text was updated successfully, but these errors were encountered: