New minetest version scheme
Posted: Sun Aug 20, 2017 15:33
After discussions, everybody in the coredev team agreed we should change the version scheme of Minetest.
This will permit to maintain easily two dev branches with various versions, whereas before it was impossible to distinguish if a player is on a stable-0.4 (0.4.17) or master (0.5.0).
It also make clear for everybody on which branch a client/server is.
Before
Dev version was {last_version}-dev
Release version was {new_version}
Example: when developping minetest 0.4.16, the dev version was 0.4.15-dev
Thanks for reading
After
Dev version is {new_version}-dev
Release version will be {new_version}
We develop minetest 0.5.0-dev, and will release minetest 0.5.0
This will permit to maintain easily two dev branches with various versions, whereas before it was impossible to distinguish if a player is on a stable-0.4 (0.4.17) or master (0.5.0).
It also make clear for everybody on which branch a client/server is.
Before
Dev version was {last_version}-dev
Release version was {new_version}
Example: when developping minetest 0.4.16, the dev version was 0.4.15-dev
Thanks for reading
After
Dev version is {new_version}-dev
Release version will be {new_version}
We develop minetest 0.5.0-dev, and will release minetest 0.5.0