From 124c8d43d3491042b330ab4806c7b542af861831 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Tue, 12 Jan 2021 09:22:06 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- proposals/2844-global-versioning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/2844-global-versioning.md b/proposals/2844-global-versioning.md index 431d85b1..0f2d4c66 100644 --- a/proposals/2844-global-versioning.md +++ b/proposals/2844-global-versioning.md @@ -30,7 +30,7 @@ contain specification). Room versions are a bit more nuanced though, and are cov The version which covers the entire specification and all its parts is called the "Matrix version", and is a promotion of the previously marketing-only version number assigned to the spec. The first version -after this proposal is expected to be Matrix 1.1, though the spec core team will make that distinction. +after this proposal is expected to be Matrix 1.1, though the spec core team will make that decision. v1.0 would be left in the marketing era and recorded for posterity (though still retains no significant meaning). @@ -76,7 +76,7 @@ See the section on brewing Matrix versions for information on how the unstable v `MINOR` versions have a backwards compatibility scheme described later in this proposal. `MAJOR` versions are expected to have zero backwards compatibility guarantees to them. -For clarity, `v1.2.0` will probably work with `v1.1.0`, though implementations should be wary if they +For clarity, `v1.2` will probably work with `v1.1`, though implementations should be wary if they depend on a version. As mentioned, the backwards compatibility scheme section goes into more detail on this.