-
Notifications
You must be signed in to change notification settings - Fork 379
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
MSC2324: Facilitating early releases of software dependent on spec #2324
Conversation
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.
lgtm, though a couple of suggestions
Co-Authored-By: Matthew Hodgson <matthew@matrix.org>
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.
Looks mostly good with just a couple of nits
Mostly stuff that has been discussed in comments, a bit of common sense, and a hint of clarity.
Team member @turt2live has proposed to merge this. The next step is review by the rest of the tagged people: No concerns currently listed. Once at least 75% of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
this lgtm - only one minor tweak to try to resolve the "you don't have to implement before you call FCP, but FCP requires evidence typically in the form of an implementation" paradox. |
Co-Authored-By: Matthew Hodgson <matthew@matrix.org>
To reiterate: | ||
|
||
* Implementations MUST NOT use stable endpoints before the MSC is in the spec. This | ||
includes NOT using stable endpoints post-FCP. |
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.
Between fcp and spec release, presumably?
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.
yup
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
It would be good to get https://matrix.org/docs/spec/proposals updated to reflect this. |
We've been using this in practice for a while now, so we should document it more officially. MSC: #2324
Spec PR: #2433 |
Merged 🎉 |
Rendered