From 79b2e5263d296a735d3346bf4eb8882841671fb6 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Sat, 7 Mar 2020 14:05:05 -0700 Subject: [PATCH] Update specification/proposals_intro.rst Co-Authored-By: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- specification/proposals_intro.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/proposals_intro.rst b/specification/proposals_intro.rst index c3b312ce..5ee82dc3 100644 --- a/specification/proposals_intro.rst +++ b/specification/proposals_intro.rst @@ -393,7 +393,7 @@ The process for an implementation willing to be ahead of a spec release is: to provide forwards/backwards compatibility - e.g. a user authentication change which can't be safely rolled back), the implementation should not attempt to implement the feature and should instead wait for a spec release. - * If at any point the idea changes, the feature flag should also change so that + * If at any point after early release, the idea changes in a backwards-incompatible way, the feature flag should also change so that implementations can adapt as needed. 3. In parallel, or ahead of implementation, open an MSC and solicit review per above.