JEP 223: New Version-String Scheme

[Magnus Ihse Bursie]

On 2014-11-07 13:39, Magnus Ihse Bursie wrote:
> 3) Using a different marker than "-" for introducing $OPT, e.g. 
> underscore.
>
> For instance, 9.0.0_foo-opt or 9.0.0-ea-_foo-opt. I think this is a 
> better solution than the ones above, but it is not ideal. It also 
> differs from the semantic versioning rules.

Correction; my example was intented to be " 9.0.0-ea_foo-opt".


Also, I'd like to make sure I understand the exampel given in the JEP:

> The sequence of numerals in a version number is compared to another 
> such sequence in numerical, pointwise fashion; /e.g./, |9.9.1| is less 
> than |9.10.0|.

Am I correct in understanding that if once a 9.9.1 released, then 9.10.0 
could never be released (since that would mean breaking the rule of 
monotonically incrementing security numbers)? But if 9.10.0 was released 
directly after 9.9.0, then later on 9.9.1 could be released. So this 
means that while 9.10.0 is in some way "newer" since the minor version 
is higher, it is also "older" in that it was released cronologically 
earlier, and does not contain the newest security fixes. I think the 
versioning scheme makes sense, but this situation is perhaps not 
completely intuitive, and could perhaps be expanded upon in either the 
JEP or in any other resulting document that will describe the new 
version system. Maybe what I'm getting at is some kind of discussion on 
the semantic meaning of ordering two version strings, not just technical 
discussions on how such ordering is to be achieved.

/Magnus