Shouldn't Minetest 5.0.0 actually be called...

Post Reply
SKCro
New member
Posts: 5
Joined: Fri Mar 08, 2019 19:03
IRC: SKCro
In-game: SKCro

Shouldn't Minetest 5.0.0 actually be called...

by SKCro » Post

Hey everyone,

I know I'm new here, but:
Shouldn't the new Minetest 5.0.0 release actually be called "Minetest 0.5"? If you actually made the first stable (neither alpha or beta) version of Minetest, it should be called "Minetest 1.0" not "Minetest 5.0".
EDIT: It should be called "Minetest 0.5" because the previous version of Minetest has "Minetest 0.4.17.1" in the title bar, and it doesn't make sense to skip all the way to Minetest 5.0...

This is the way it should be (but imagine it saying "Minetest 0.5" instead of "Minetest 0.4.17.1"):
VersionNumberPic1.PNG
(86.35 KiB) Not downloaded yet
This is NOT the way it should be:
VersionNumberPic2.PNG
(48.15 KiB) Not downloaded yet
Your new beta tester,
SKCro

sofar
Developer
Posts: 2132
Joined: Fri Jan 16, 2015 07:31
GitHub: sofar
IRC: sofar
In-game: sofar

Re: Shouldn't Minetest 5.0.0 actually be called...

by sofar » Post

SKCro wrote:Hey everyone,

I know I'm new here, but:
Shouldn't the new Minetest 5.0.0 release actually be called "Minetest 0.5"? If you actually made the first stable (neither alpha or beta) version of Minetest, it should be called "Minetest 1.0" not "Minetest 5.0".
EDIT: It should be called "Minetest 0.5" because the previous version of Minetest has "Minetest 0.4.17.1" in the title bar, and it doesn't make sense to skip all the way to Minetest 5.0...

This is the way it should be (but imagine it saying "Minetest 0.5" instead of "Minetest 0.4.17.1"):
VersionNumberPic1.PNG
This is NOT the way it should be:
VersionNumberPic2.PNG
Your new beta tester,
SKCro
no

User avatar
benrob0329
Member
Posts: 1321
Joined: Thu Aug 06, 2015 22:39
GitHub: Benrob0329
IRC: benrob0329
In-game: benrob03
Location: Michigan
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by benrob0329 » Post

The developers switched to a sane versioning scheme, and wanted to avoid the press of "the 1.0 release".

Its not wrong, its still a larger number and a lot of people got confused by the leading 0 anyways.
Social: YouTube Peertube Matrix Room: #minetest:matrix.org | Games: The Infinite IKEA

SKCro
New member
Posts: 5
Joined: Fri Mar 08, 2019 19:03
IRC: SKCro
In-game: SKCro

Re: Shouldn't Minetest 5.0.0 actually be called...

by SKCro » Post

Why would they want to avoid "Minetest 1.0"? Its weird that they skipped to 5.0 and never did 2.0, 3.0, or 4.0...

-SKCro

User avatar
benrob0329
Member
Posts: 1321
Joined: Thu Aug 06, 2015 22:39
GitHub: Benrob0329
IRC: benrob0329
In-game: benrob03
Location: Michigan
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by benrob0329 » Post

Because "1.0" would imply a fully finished product, which MT will likely never be due to the nature of it's development. So they decided to just drop the leading zero.
Social: YouTube Peertube Matrix Room: #minetest:matrix.org | Games: The Infinite IKEA

User avatar
sorcerykid
Member
Posts: 1342
Joined: Fri Aug 26, 2016 15:36
GitHub: sorcerykid
In-game: Nemo
Location: Illinois, USA

Re: Shouldn't Minetest 5.0.0 actually be called...

by sorcerykid » Post

Minetest actually underwent two changes to the versioning scheme almost concurrently.

The first change was to renumber development builds based on the forthcoming release (whereas before it was derived from the previous stable branch). I brought up this concern a couple years ago, as it was causing a great deal of confusion when distinguishing between stable and development builds. That seemed to generate enough interest that the core developers opted for a saner versioning scheme.

viewtopic.php?p=285668#p285668
viewtopic.php?p=288006#p288006
viewtopic.php?f=18&t=18331

The second change was to adopt a variation of SemVer, as both the engine and the game long since surpassed the alpha stage. Core developers discussed this thoroughly on GitHub and IRC before reaching a consensus. It was decided that removing the preceding zero would ensure a greater sense of continuity between releases. Also some users were already referring to Minetest 0.5.0 as "5.0".

viewtopic.php?p=322733#p322733
viewtopic.php?p=322837#p322837
http://irc.minetest.net/minetest-dev/2018-06-13

Here's the GitHub issue where both matters were addressed: https://github.com/minetest/minetest/issues/6073

User avatar
Andrey01
Member
Posts: 2395
Joined: Wed Oct 19, 2016 15:18
GitHub: Andrey2470T
In-game: Andrey01
Location: Russia, Moscow

Re: Shouldn't Minetest 5.0.0 actually be called...

by Andrey01 » Post

SKCro wrote:Why would they want to avoid "Minetest 1.0"? Its weird that they skipped to 5.0 and never did 2.0, 3.0, or 4.0...

-SKCro
They used to skip nowhere. The core devs just got rid of unnecessary "0." in the beginning of each version, that`s all.

User avatar
v-rob
Member
Posts: 752
Joined: Thu Mar 24, 2016 03:19
GitHub: v-rob
Location: Right behind you.

Re: Shouldn't Minetest 5.0.0 actually be called...

by v-rob » Post

Actually, this happened before as well. In the super early alpha versions, it went from 0.0.1 to 0.2, so this would make it the second time a leading zero has been dropped.

User avatar
MineYoshi
Member
Posts: 5373
Joined: Wed Jul 08, 2015 13:20
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by MineYoshi » Post

You know, devs here do whatever they want and we comply with them without greater hassle.

Try to find some "real" bugs instead if you want to help the game's development.
Oi

Gibeinumo
Member
Posts: 30
Joined: Tue Oct 23, 2018 07:19

Re: Shouldn't Minetest 5.0.0 actually be called...

by Gibeinumo » Post

Wow, it is called 5.0 and not 0.5. It took me six days until I realized it. I guess it does make sense because it already is a playable, good game.

User avatar
Linuxdirk
Member
Posts: 2554
Joined: Wed Sep 17, 2014 11:21
In-game: Linuxdirk
Location: Germany
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by Linuxdirk » Post

sorcerykid wrote:It was decided that removing the preceding zero […]
The bogus version number now being used as base for future versions is always justified with “oh, we’re just removing the leading zero” but what was actually done is simply skipping to the 5th major version in the version number scheme that was used before.

Like with Chrome or Firefox releasing a new major version for every minor set of changes just to have a higher number. Or like Nvidia coming closer to major version 400 with their drivers with every release.

This is just ridiculous.

Skulls
Member
Posts: 108
Joined: Thu Dec 21, 2017 17:41
In-game: Skulls

Re: Shouldn't Minetest 5.0.0 actually be called...

by Skulls » Post

If you are looking for more information in a version number than it being before the things after or after the things before you are overloading that poor number and should show some kindness to your data structures.

It's a number that goes up. Everything important is in the change log.

User avatar
sorcerykid
Member
Posts: 1342
Joined: Fri Aug 26, 2016 15:36
GitHub: sorcerykid
In-game: Nemo
Location: Illinois, USA

Re: Shouldn't Minetest 5.0.0 actually be called...

by sorcerykid » Post

Linuxdirk wrote: The bogus version number now being used as base for future versions is always justified with “oh, we’re just removing the leading zero” but what was actually done is simply skipping to the 5th major version in the version number scheme that was used before.
That's not true because the version scheme changed. It wasn't as simple as just removing the leading zero (altho that was a justification for consistency's sake). But in truth, 0.4.x and earlier releases used a version scheme that was contrived specifically for Minetest development. Even core devs admitted this on IRC. Following that unofficial "convention", the second number represented a breaking change. In contrast, the current version scheme is more closely related to the SemVer standard, in which the first number represents a breaking change. Hence, 0.5.0 is correctly translated to 5.0.

User avatar
Linuxdirk
Member
Posts: 2554
Joined: Wed Sep 17, 2014 11:21
In-game: Linuxdirk
Location: Germany
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by Linuxdirk » Post

Yes, this is how it was justified afterwards. Minetest never used semantic versioning and does not use it with 5.0.0. The version number is just nonsense, or as Skulls said: "It's a number that goes up. Everything important is in the change log."

User avatar
rubenwardy
Moderator
Posts: 6193
Joined: Tue Jun 12, 2012 18:11
GitHub: rubenwardy
IRC: rubenwardy
In-game: rubenwardy
Location: United Kingdom
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by rubenwardy » Post

Minetest does now follow semver, with slight changes to how we label development versions

User avatar
sorcerykid
Member
Posts: 1342
Joined: Fri Aug 26, 2016 15:36
GitHub: sorcerykid
In-game: Nemo
Location: Illinois, USA

Re: Shouldn't Minetest 5.0.0 actually be called...

by sorcerykid » Post

Um no, this was not how it was justified afterward :P Please read the IRC log from June 3, 2017.

http://irc.minetest.net/minetest-dev/2017-06-03

You'll see there was an intensive discussion between Wuzzy, VanessaE, and the core devs about finally adopting semantic versioning a full year prior to the paramat's proposal on issue #6073 about dropping the leading zero from 0.5.0.The core devs were legitimately trying to adhere to the SemVer standard (except for labels of development builds as rubenwardy stated), not just using it as an excuse to bump the version to 5.0.

Punk
Member
Posts: 158
Joined: Sun Dec 25, 2016 06:52

Re: Shouldn't Minetest 5.0.0 actually be called...

by Punk » Post

It's to match the kernel 5.0.

User avatar
rubenwardy
Moderator
Posts: 6193
Joined: Tue Jun 12, 2012 18:11
GitHub: rubenwardy
IRC: rubenwardy
In-game: rubenwardy
Location: United Kingdom
Contact:

Re: Shouldn't Minetest 5.0.0 actually be called...

by rubenwardy » Post

Punk wrote:It's to match the kernel 5.0.
Nah, pretty sure they copied us

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests