Proposal: Newer version-string scheme for the Java SE Platform and the JDK (original) (raw)
Remi Forax forax at univ-mlv.fr
Thu Nov 2 22:22:16 UTC 2017
- Previous message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Next message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Stephen, as John said, have a bijection between the JVM version and the Java version.
and practically, given the backlog of VM spec changes we had actually, i will not be too worry of having a Java feature release without the JVM changes :)
cheers, Rémi
----- Mail original -----
De: "Stephen Colebourne" <scolebourne at joda.org> À: "jdk-dev" <jdk-dev at openjdk.java.net> Envoyé: Jeudi 2 Novembre 2017 23:10:56 Objet: Re: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
On 2 November 2017 at 21:21, John Rose <john.r.rose at oracle.com> wrote:
In that environment, would you rather have a predictable lock-step rule for tool development, or would you still prefer your scheme, which optimizes for the infrequent "null" change, at the cost of guessing on a random variable? If the JVM/bytecode level has not changed, I can't see any advantages to anyone outside Oracle/OpenJDK of a version bump. Stephen
- Previous message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Next message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]