summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorLoïc Blot <nerzhul@users.noreply.github.com>2018-06-15 09:16:48 +0200
committerGitHub <noreply@github.com>2018-06-15 09:16:48 +0200
commitac6e8e2914888d77625bb3b67ff6aaea9fc6cbab (patch)
tree8ea85a622fb227780a95e50ef0dc7f798b990bb4 /README.md
parent2bec28f4621fee5ff72a0edc8065d33c2bcd1d48 (diff)
downloadminetest-ac6e8e2914888d77625bb3b67ff6aaea9fc6cbab.tar.gz
minetest-ac6e8e2914888d77625bb3b67ff6aaea9fc6cbab.tar.bz2
minetest-ac6e8e2914888d77625bb3b67ff6aaea9fc6cbab.zip
Version scheme change: 0.5.0 -> 5.0.0 (#7449)
* Version scheme change: 0.5.0 -> 5.0.0
Diffstat (limited to 'README.md')
-rw-r--r--README.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/README.md b/README.md
index 61cf57175..ebfad24be 100644
--- a/README.md
+++ b/README.md
@@ -431,9 +431,11 @@ This is how we build Windows releases.
Version scheme
--------------
-Minetest doesn't follow semver. Instead, we do something roughly similar to 0.major.minor.
+Minetest partially follows semver (major.minor.patch).
-Since 0.5.0-dev and 0.4.17-dev, the dev notation refers to the next release,
-ie: 0.5.0-dev is the development version leading to 0.5.0.
+Since 5.0.0-dev and 0.4.17-dev, the dev notation refers to the next release,
+ie: 5.0.0-dev is the development version leading to 5.0.0.
Prior to that, we used oldversion-dev.
+
+Semver was adopted after 0.4.X series. Before that we used 0.major.minor scheme.