Minetest Forums

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

Good change :)

But for people doing packaging, please keep in mind, that a version like 0.5.0-dev-20170820 will be interpreted as newer than 0.5.0 in most packaging systems. It's probably better to use 0.5.0~dev-20170820 (or similar), that should result in a lower version than 0.5.0.

nrz wrote: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

So just like it used to be in older versions

And where exactly is this written down? The forum alone is not enough IMO.

Wuzzy wrote:And where exactly is this written down? The forum alone is not enough IMO.

It's also in the read me

Well, everything's fine, then! :-)

i don't find any wiki page about this, but maybe it can be an idea to add it to dev wiki