Version 0.15.40

[mexmer]

if you keep on bringing out these minor updates you'll eventually reach 0.15.99 and have no choice but to bring out 0.16.0

That's not how their version numbering works, they can just do 0.15.100

So then we need to wait for them to get to 15.999? They better hurry up with those updates then.

I think it will be after 0.15.65535 or 0.15.4294967295 (depending on what versioning system in use).

Uffda... Or even 0.15.18446744073709551615

0.15.65535 is maximum we can do

if you use windows versioning, you can use also other field
in windows file version can be up to
65535.65535.65535.65535
in version property metadata, that is.

[posila]

if you use windows versioning, you can use also other field
in windows file version can be up to
65535.65535.65535.65535
in version property metadata, that is.

The point was, after 0.15.65535 we would have to release 0.16.0

[mexmer]

if you use windows versioning, you can use also other field
in windows file version can be up to
65535.65535.65535.65535
in version property metadata, that is.

The point was, after 0.15.65535 we would have to release 0.16.0

point is, you don't need to. you can realease 0.15.65535.1

windows file versioning does not support letters in file version, so you can't go with something like 0.15.65535a and similar tho'

you can have version resource string, which can be anything, but fileversion is number (or rather 4 16bit numbers) ... if we talking about windows files resources ... on other systems, it's different, but your primary platform is windows, if i'm not mistaken.

[kovarex]

if you use windows versioning, you can use also other field
in windows file version can be up to
65535.65535.65535.65535
in version property metadata, that is.

The point was, after 0.15.65535 we would have to release 0.16.0

point is, you don't need to. you can realease 0.15.65535.1

windows file versioning does not support letters in file version, so you can't go with something like 0.15.65535a and similar tho'

you can have version resource string, which can be anything, but fileversion is number (or rather 4 16bit numbers) ... if we talking about windows files resources ... on other systems, it's different, but your primary platform is windows, if i'm not mistaken.

Just to let you know, we don't really use windows versioning, we can make our version to be whatever

[mexmer]

if you use windows versioning, you can use also other field
in windows file version can be up to
65535.65535.65535.65535
in version property metadata, that is.

The point was, after 0.15.65535 we would have to release 0.16.0

point is, you don't need to. you can realease 0.15.65535.1

windows file versioning does not support letters in file version, so you can't go with something like 0.15.65535a and similar tho'

you can have version resource string, which can be anything, but fileversion is number (or rather 4 16bit numbers) ... if we talking about windows files resources ... on other systems, it's different, but your primary platform is windows, if i'm not mistaken.

Just to let you know, we don't really use windows versioning, we can make our version to be whatever

that's what i thought, that why there is if in my first comment on this