JDK 9 Release Candidate process proposal

jesper.wilhelmsson at oracle.com jesper.wilhelmsson at oracle.com
Mon Jun 19 19:36:10 UTC 2017

That's one way of postponing something for a while. But at least it won't be permanently forgotten as is a huge risk when setting the fix version to "sometime in the future".

> On 19 Jun 2017, at 20:09, Martin Buchholz <martinrb at google.com> wrote:
> Interesting.  It seems  "Fix Version = 13" is the new "leaving Fix Version blank".
> https://bugs.openjdk.java.net/issues/?filter=25118&jql=fixVersion%20%3D%2013 <https://bugs.openjdk.java.net/issues/?filter=25118&jql=fixVersion%20%3D%2013>
> On Mon, Jun 19, 2017 at 7:33 AM, <jesper.wilhelmsson at oracle.com <mailto:jesper.wilhelmsson at oracle.com>> wrote:
> Please note that for any bugs in the hotspot and core-svc component stricter rules around fix versions are applied.
> In these areas all bugs needs to have a valid JDK version as fix version (a value like 10, 11, 12, etc). Leaving the fix version blank is not an option and the buckets tbd_minor and tbd_major are not used. Buckets like 8-pool and 9-pool are only used for backports.

More information about the jdk9-dev mailing list