JEP 223: New Version-String Scheme

[Iris Clark]

Hi, Magnus.

Thank you so much for your comments.  I apologize for the delay in replying.  I'm still recovering from recent IT changes.  I hoping that I've gotten past the worst bits.

Let me answer the easy message first.

> 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)?

No.  Given versions 9.9.1, and 9.10.0, you can say is that 9.9.1 is more secure and has fewer features than 9.10.0.  You can also say that 9.9.1 is "less than" 9.10.0 since version numbers are compared lexicographically.  9.10.0 can be released any time relative to 9.9.1. 

> 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.

I'm working to add text to the JEP to provide more details around ordering.  As I work through those changes, I'll be working out a reply to your other message.

Thanks,
iris

-----Original Message-----
From: Magnus Ihse Bursie 
Sent: Friday, November 07, 2014 6:34 AM
To: platform-jep-discuss at openjdk.java.net
Subject: Re: JEP 223: New Version-String Scheme

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