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
New minetest version scheme
-
- Member
- Posts: 252
- Joined: Tue Sep 23, 2014 16:02
- GitHub: lnjX
- IRC: LNJ
- In-game: LNJ
- Location: Europe/Berlin
Re: New minetest version scheme
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.
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.
Storage Drawers - The simplest item storage in Minetest
-
- Member
- Posts: 197
- Joined: Tue Dec 24, 2013 17:01
- GitHub: chaoswormz
- IRC: CWz
- In-game: CWz
- Location: Banana Land
Re: New minetest version scheme
So just like it used to be in older versionsnrz 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
- Wuzzy
- Member
- Posts: 4803
- Joined: Mon Sep 24, 2012 15:01
- GitHub: Wuzzy2
- IRC: Wuzzy
- In-game: Wuzzy
- Contact:
Re: New minetest version scheme
And where exactly is this written down? The forum alone is not enough IMO.
- rubenwardy
- Moderator
- Posts: 6978
- Joined: Tue Jun 12, 2012 18:11
- GitHub: rubenwardy
- IRC: rubenwardy
- In-game: rubenwardy
- Location: Bristol, United Kingdom
- Contact:
Re: New minetest version scheme
It's also in the read meWuzzy wrote:And where exactly is this written down? The forum alone is not enough IMO.
- Wuzzy
- Member
- Posts: 4803
- Joined: Mon Sep 24, 2012 15:01
- GitHub: Wuzzy2
- IRC: Wuzzy
- In-game: Wuzzy
- Contact:
Re: New minetest version scheme
Well, everything's fine, then! :-)
-
- Developer
- Posts: 131
- Joined: Sat Feb 07, 2015 17:16
- GitHub: nerzhul
- IRC: nrzkt
- In-game: nrz
- Location: France
- Contact:
Re: New minetest version scheme
i don't find any wiki page about this, but maybe it can be an idea to add it to dev wiki
Who is online
Users browsing this forum: No registered users and 4 guests