-
-
Notifications
You must be signed in to change notification settings - Fork 405
Add room upgrading guide #2861
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
Add room upgrading guide #2861
Conversation
Co-Authored-By: Cat <catalanlover@protonmail.com> Co-Authored-By: Gnuxie <Gnuxie@protonmail.com> Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
|
We would welcome any help to turn this current draft into a proper text. If you have time and would like to contribute by turning bullet points into text, please submit suggestions by reviewing this PR! We think we have covered the essential points, but of course additions are also welcome! |
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Deploying matrix-website with
|
| Latest commit: |
f4becf0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4c2ea5fd.matrix-website.pages.dev |
| Branch Preview URL: | https://harharlinks-room-upgrading-g.matrix-website.pages.dev |
|
Pleased to see progress on this! Please tag me for a review ahead of publication, I'll pop it to the top of my list. |
Co-authored-by: Tobias Fella <9750016+TobiasFella@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
@jimmackenzie please take a look! |
|
We've planned to release it soon. |
Good from my side, please review. Also need a review from the foundation. Idea to copy the same thing to the blog is still up in the air. Need info from @jimmackenzie to align about what is planed from foundation side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving because imperfect doc is better than no docs, but there are a few nits
|
|
||
| **Advanced upgrading:** | ||
| There are some reasons why your client might not be showing you the upgrading UI despite an upgrade being available, including: | ||
| - Your homeserver implementation or admin doesn't recommend it, via the [homeserver's configuration](https://spec.matrix.org/latest/client-server-api/#mroom_versions-capability). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused that this talks about homeserver config and links to the spec that doesn't.
Starting my review now. |
jimmackenzie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, with a number of suggestions (removing passive voice, simplifying some sentences and formatting suggestions). Also incorporated some suggestions from the other reviewers.
Co-authored-by: David Mehren <git@herrmehren.de> Co-authored-by: Thibault Martin <thibaultamartin@users.noreply.github.com>
Co-authored-by: Jim Mackenzie <jimm@element.io>
Co-authored-by: Jim Mackenzie <jimm@element.io>
KitsuneRal
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding Quaternion to the lists.
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Co-authored-by: Alexey Rusakov <Kitsune-Ral@users.sf.net>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Co-authored-by: Jim Mackenzie <jimm@element.io>
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
|
Results from testing session: Upgrading an invite-only room does not invite the member users. Former room members get strange errors in Element X if they are not invited as the try to click the button in the old room. |
Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
|
Huuuge thanks to all involved: the T&S WGs contributing to the collection of info at #2704, @davidmehren for co-working heavily on reviews at the #WHY2025 chaos-DACH co-working office, @thibaultamartin and @jimmackenzie from the Foundation side, all other reviewers not visible here, and all client developers contributing info about their feature level here or elsewhere. |
| - Quaternion | ||
| - FluffyChat | ||
| - Cinny | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
< polycule > supports the same syntax as well.
| - Cinny | ||
| - Tammy | ||
| - Nheko | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
< polycule > can tombstone into new rooms as well.
🎩 Website & Content WG in collaboration with T&S R&D WG
Signed-off-by: HarHarLinks 2803622+HarHarLinks@users.noreply.github.com
Tackles #2704, though there may be multiple iterations in this or in followup-PRs - depends on the Hydra release timeline and contributor availabilities so the exact approach remains to be seen.
The plan is to also(?) release a blog post or incorporate this somehow into a blog post shortly before the Hydra release.
The prioritization/planned iterations are:
✔️ Checklist
<>to linkify them (learn more).[label](@/target.md)syntax./blogpage, especially for multiple posts on the same day. Prefer UTC format, e.g.2025-12-01T14:00:00Zfor Dec 1st, 2025, 2pm UTC.