JDK 9 is not (yet) Feature Complete -- how will we get there?

mark.reinhold at oracle.com mark.reinhold at oracle.com
Tue Jun 21 22:09:42 UTC 2016

2016/6/15 12:23:29 -0700, vladimir.kozlov at oracle.com:
> I would suggest to have a link to the latest webrev in JBS, when it is
> ready, to see the scope of changes.

This might be appropriate for a small change prior to requesting an FC
extension, but someone responsible for a larger change will likely want
to request (and receive) an extension before finishing up all the work,
so I don't think we can mandate this for all requests.

> And to have ability to change jdk9-fc-yes (approved) to jdk9-fc-no
> (rejected) if scope of final changes is larger than initially
> described in FC Extension Request.

I don't think this sort of case needs to be baked into the process.
If a Lead who has previously approved a request later sees that it's
grown dramatically in scope then they should contact the responsible
developer directly.  This may result in the issue being closed or
targeted to a later release.  Replacing the jdk9-fc-yes label with
jdk9-fc-no isn't really needed, but it wouldn't hurt.

- Mark

More information about the jdk9-dev mailing list