News for hackers. Stuff that matters.
Re:Wine 4.20 by cranky_coder on Sunday November 17, 2019 @03:08AM (#21557021)
Why was this title changed? It’s just downright inaccurate now? The linked release is 4.20
Re:Wine 4.20 by mdf on Sunday November 17, 2019 @03:29AM (#21557072)
Indeed. Even with some versioning schemes where 4.2 would equal 4.20 I wouldn't see the point in changing the title from what the project itself used. And if I'm reading this[1] correctly, the versions look pretty straightforward (i.e. 4.1 < 4.10 etc.).

[1] https://github.com/wine-mirror/wine/commits/master/VERSION

Re:Wine 4.20 by robjan on Sunday November 17, 2019 @03:30AM (#21557077)
Looks like semver to me but with x.y instead of x.y.z
Re:Wine 4.20 by andrewshadura on Sunday November 17, 2019 @04:15AM (#21557159)
I agree. 4.2 was released in February: https://www.winehq.org/news/2019021501
Re:Wine 4.20 by YokoZar on Sunday November 17, 2019 @03:10AM (#21557025)
Note that Wine is one of those confusingly-versioned projects where 4.20 is the one that comes after 4.19
Re:Wine 4.20 by viraptor on Sunday November 17, 2019 @03:35AM (#21557086)
I would say that's like pretty much every project out there. I can't come up with an example which matches the other case off the top of my head. Does that make other ones the confusing ones?
Re:Wine 4.20 by YokoZar on Sunday November 17, 2019 @03:58AM (#21557130)
It's less confusing when there is more than 1 decimal point. 4.11.4 is clearly not a regular decimal number.
Re:Wine 4.20 by dtech on Sunday November 17, 2019 @04:54AM (#21557247)
I don't know of any other software where x.10 does not come after x.9, or x.20 does not come after x.19 etc.

Some software increases the x before that though.

Re:Wine 4.20 by SyneRyder on Sunday November 17, 2019 @07:13AM (#21557602)
Winamp used a decimal numbering scheme. Version 5.6 is followed by 5.601, then 5.62. There's also the obligatory v1.6 < v1.666 < v1.7 version numbering of Doom.

I think Windows 3.1 to 3.11 was another example of decimal version numbering, instead of calling it v3.1.1.

Re:Wine 4.20 by chme on Sunday November 17, 2019 @05:17AM (#21557293)
Blenders version is a bit confusing sometimes. Officially its release 2.80 but that is very often called 2.8 even from official channels [1]. I was a bit confused when then announced 2.8 which is the version after 2.79.

[1] https://code.blender.org/2018/11/blender-2-8-beta/

Re:Wine 4.20 by filmor on Sunday November 17, 2019 @05:59AM (#21557388)
They always count from 00 onwards with a leading 0, though (x.01, ... x.09, x.10 etc.).

The equivalent in the more common versioning scheme would be 2.8.0 which would then also be called 2.8.

Re:Wine 4.20 by chme on Sunday November 17, 2019 @06:26AM (#21557472)
Well their scheme does leave some questions open: Does 3.00 need to come after 2.99 or can there be a 2.100? Or if its more like 2.8.x: Can ever be a x.x.10? (we are talking here more about the scheme that actual blender releases)

How I currently understand is its just 2 numbers and 2.8 is a simplification for meaning 2.8x.

Re:Wine 4.20 by stkdump on Sunday November 17, 2019 @04:20AM (#21557168)
What would non-confusingly come after 4.19, just out of interest?
Re:Wine 4.20 by mariomeissner on Sunday November 17, 2019 @04:23AM (#21557181)
He's probably thinking about decimal numbers, so 4.2 is expected instead of 4.20
Re:Wine 4.20 by MaxBarraclough on Sunday November 17, 2019 @05:34AM (#21557335)