Proposal: Newer version-string scheme for the Java SE Platform and the JDK (original) (raw)
Stephen Colebourne scolebourne at joda.org
Thu Nov 2 22:10:56 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 ]
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 ]