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}-devRelease version was {new_version}

Example: when developping minetest 0.4.16, the dev version was 0.4.15-dev

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}-devRelease version was {new_version}

Example: when developping minetest 0.4.16, the dev version was 0.4.15-dev