Version scheme change: 0.5.0 -> 5.0.0 (#7449)

* Version scheme change: 0.5.0 -> 5.0.0
This commit is contained in:
Loïc Blot 2018-06-15 09:16:48 +02:00 committed by GitHub
parent 2bec28f462
commit ac6e8e2914
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 9 additions and 7 deletions

@ -15,8 +15,8 @@ set(GCC_MINIMUM_VERSION "4.8")
set(CLANG_MINIMUM_VERSION "3.4")
# Also remember to set PROTOCOL_VERSION in network/networkprotocol.h when releasing
set(VERSION_MAJOR 0)
set(VERSION_MINOR 5)
set(VERSION_MAJOR 5)
set(VERSION_MINOR 0)
set(VERSION_PATCH 0)
set(VERSION_EXTRA "" CACHE STRING "Stuff to append to version string")

@ -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.

@ -1,4 +1,4 @@
Minetest Lua Client Modding API Reference 0.5.0
Minetest Lua Client Modding API Reference 5.0.0
================================================
* More information at <http://www.minetest.net/>
* Developer Wiki: <http://dev.minetest.net/>

@ -1,4 +1,4 @@
Minetest Lua Mainmenu API Reference 0.5.0
Minetest Lua Mainmenu API Reference 5.0.0
========================================
Introduction