Feedback on Handling of Transition to Matrix 1.1 #2027
Description
Your use case
Greetings,
First I want to share my appreciation for the work that you all do in maintaining this client and the contributions to the Matrix ecosystem at large.
The release of v1.11.40 included PR #9819. In short, I feel there's not enough disapproval or voiced frustration in how this change was handled.
Best I can tell, the potential impact of the PR was under-communicated, or I fear worse: not communicated.
With this latest release, those running older and/or legacy versions of synapse are now forced to:
- Use an alternate client,
- Rollback Element to a previous version, or
- Update to a more contemporary version of synapse.
While I think it's fair that operators should not assume that old versions will work in perpetuity, there are situations where operators can not easily update their legacy deployments without going through their own change management processes (e.g. highly regulated environments).
Changes which have the opportunity to impact users should be broadly announced ahead of their release, allowing operators sufficient runway to respond and take action.
This release has likely impacted the business and communication continuity of countless users and made administrators scramble.
Have you considered any alternatives?
No response
Additional context
No response