From c8ceb59597ae61893341705ed7270a152636919e Mon Sep 17 00:00:00 2001 From: lararennie Date: Wed, 19 Apr 2017 13:53:42 +0200 Subject: [PATCH] Tiny clarification to versioning policy (#1689) --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5c0182bb1..8d142bdce 100644 --- a/README.md +++ b/README.md @@ -55,11 +55,13 @@ building, we publish a major release. For example, if the last release were 7.7.3, the new one would be 8.0.0. If any of those changes *enable* clients to update their code to take advantage -of new functionality, we publish a minor release. So we'd go from 7.7.3 to -7.8.0. +of new functionality, and if clients would have to roll-back these changes in +the event that the release was marked as "bad", we publish a minor release. For +example, we'd go from 7.7.3 to 7.8.0. -Otherwise, including when a release contains only [metadata](FAQ.md#metadata_definition) -changes, we publish a sub-minor release, e.g. 7.7.3 to 7.7.4. +Otherwise, including when a release contains only +[metadata](FAQ.md#metadata_definition) changes, we publish a sub-minor release, +e.g. 7.7.3 to 7.7.4. Sometimes we make internal changes to the code or metadata that, while not affecting compatibility for clients, could affect compatibility for **porters**