JEP 223: New Version-String Scheme

[Iris Clark]

Hi, Jorn.

Thanks for you comments.  Here are some answers.

> I’ve found a small typo in JEP 223 /
> https://bugs.openjdk.java.net/browse/JDK-8061493
>
> The line
> "Security 2014/04    1.7.0_55-b13    7u55    7.6.14+13    7.5.14"
> should be
> "Security 2014/04    1.7.0_55-b13    7u55    7.5.14+13    7.5.14"

Yes, the $MAJOR value should not have changed.  Updated.

> Is the JEP at http://openjdk.java.net/jeps/223 being kept in sync with
> https://bugs.openjdk.java.net/browse/JDK-8061493 or does the issue override
> the JEP?

The content of the JEP (.../jeps/223) is pulled from the bug JDK-8061493.  If
they're not in sync that indicates a problem with the server doing the pull.

> What’s the status of JEP 223? Will it definitely be included in Java 9?

JEP 223 is currently targeted for JDK 9 (see the "Status" and "Release"
fields).

A complete list of JEPs targeted for JDK 9 may be found on the JDK 9 Project
page: http://openjdk.java.net/projects/jdk9/ .

> Latest EA gives me this:
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b72) 
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b72, mixed mode)
>
> Is there an ETA when this will be included so we can test with the new
> version scheme? 

Feature complete for JDK 9 is currently scheduled for December 2015.  We hope
to be done before then.

At present, development is being done in OpenJDK Project Verona [0].  The
latest changes are in that Project's staging repository [1].  It was last
sync'd with jdk9-b71.  (The b72 sync is in progress.)  You should be able to
build and get something like this:

$ ./java -version
java version "9-internal"
Java(TM) SE Runtime Environment (build 9-internal+0-2015-07-14-120103.iris.verona)
Java HotSpot(TM) 64-Bit Server VM (build 9-internal+0-2015-07-14-120103.iris.verona, mixed mode)

Once the implementation is complete, we'll integrate into one of the JDK 9
release forests.  After that, the next JDK 9 promotion will include Verona so
you'll see the new version numbers.

> The "Pre-release identifiers are compared numerically when they consist only
> of digits, and lexicographically otherwise.” part is a bit concerning and
> doesn’t really adhere to the principle of least surprise.

> I currently handle it this way in Comparable<MyVersion>:
> http://pastebin.com/7xaizUKm …but it makes me feel kind of dirty.

> Wouldn’t it make more sense to just rule that pre should be compared
> lexicographically? I think
> https://bugs.openjdk.java.net/browse/JDK-8061493?focusedCommentId=13602386&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13602386
> has a very valid point.

Hmmm... I'm going to have to think about this.  The comparison was supposed to
attempt to align us with semver.org handling of pre-release identifiers.
There have also been some considered adjustments to that area of the spec
since it was originally written to handle specific concerns.  I'm going to
need to dig out my notes.

> I hope this is the proper way to discuss JEP 223. 

Yes, verona-dev [2] is the right place.  

> It’s not possible to just create an account for the bug tracker, right?

Correct.  To login/get an account on bugs.openjdk.java.net, you need to be
registered in the OpenJDK Census [3] (for instance by becoming a Project
Author [4]).

Thanks,
iris

[0]: http://openjdk.java.net/projects/verona
[1]: http://hg.openjdk.java.net/verona
[2]: http://mail.openjdk.java.net/mailman/listinfo/verona-dev
[3]: http://openjdk.java.net/census
[4]: http://openjdk.java.net/projects/#project-author

-----Original Message-----
From: Jörn Huxhorn [mailto:jhuxhorn at googlemail.com] 
Sent: Tuesday, July 14, 2015 2:53 AM
To: verona-dev at openjdk.java.net
Subject: JEP 223: New Version-String Scheme

I’ve found a small typo in JEP 223 / https://bugs.openjdk.java.net/browse/JDK-8061493

The line
"Security 2014/04    1.7.0_55-b13    7u55    7.6.14+13    7.5.14"
should be
"Security 2014/04    1.7.0_55-b13    7u55    7.5.14+13    7.5.14"

Is the JEP at http://openjdk.java.net/jeps/223 being kept in sync with https://bugs.openjdk.java.net/browse/JDK-8061493 or does the issue override the JEP?

What’s the status of JEP 223? Will it definitely be included in Java 9?

Latest EA gives me this:
java version "1.9.0-ea"
Java(TM) SE Runtime Environment (build 1.9.0-ea-b72) Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b72, mixed mode)

Is there an ETA when this will be included so we can test with the new version scheme?

The "Pre-release identifiers are compared numerically when they consist only of digits, and lexicographically otherwise.” part is a bit concerning and doesn’t really adhere to the principle of least surprise.

I currently handle it this way in Comparable<MyVersion>: http://pastebin.com/7xaizUKm …but it makes me feel kind of dirty.

Wouldn’t it make more sense to just rule that pre should be compared lexicographically? I think https://bugs.openjdk.java.net/browse/JDK-8061493?focusedCommentId=13602386&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13602386 has a very valid point.

I hope this is the proper way to discuss JEP 223. It’s not possible to just create an account for the bug tracker, right?

Cheers,
Jörn.