On Dec 1, 2017, at 4:41 PM, Dan Smith <daniel.sm...@oracle.com> wrote: > > I've uploaded what I believe could be a final spec for nestmates, here: > http://cr.openjdk.java.net/~dlsmith/nestmates.html > > Since October, changes include: > > - Tweaks to the explanatory material in 2.11.8 and 3.7 > > - Some restructuring of the new 5.4.4 text to be a little less disruptive and > more clearly define "same nest" and "nest host". There are some subtle > behavioral differences compared to the previous iteration when errors occur. > > - Added an example to 5.4.5 to illustrate transitive overriding > > —Dan
I suggest changing the references to 18.3 to 10, based on today's information copied below. — John http://mail.openjdk.java.net/pipermail/jdk-dev/2017-December/000301.html Begin forwarded message: > > From: mark.reinh...@oracle.com > Subject: Re: Draft JEP: Time-Based Release Versioning > Date: December 1, 2017 at 7:59:47 AM PST > To: volker.simo...@gmail.com > Cc: jdk-...@openjdk.java.net > > 2017/12/1 3:11:18 -0800, volker.simo...@gmail.com > <mailto:volker.simo...@gmail.com>: >> thanks for publishing the draft. Overall it looks good! >> >> I have just a few comment :) >> >> 1. Is thisJEP (i.e. the new version scheme) intended to be targeted >> for Java 10? > > It's intended to be targeted when it's ready, just like any other JEP. > It's obviously desirable to have it in 10, but if it doesn't make it > then it'll be in 11. > >> I would appreciate to have it in ten but aren't we already quite late? >> This is specification relevant (i.e. has to go into JSR 383) because >> it changes java.lang.Runtime.Version and various standard system >> properties which refer to it. JSR 383 has to be renamed from "Java SE >> 18.3 Platform JSR" to "Java SE 10 Platform JSR" afterwards, right? > > That should be done anyway, regardless of whether this JEP makes it into > JDK 10. If we change nothing in JDK 10, as it stands today, then the > JDK 10 GA release will identify itself as 10, not 18.3. > >
