Severin,
OpenJDK9 has reached the Release Candidate phase. I attached the
most recent e-mail on that topic. At this point in the release,
only _critical_ P1 bugs can be fixed.
Dan
On 7/7/17 7:42 AM, Severin Gehwolf wrote:
Hi,
Could somebody please approve 8181419 for JDK 9. As mentioned in the
bug, this is a stability improvement on 8153711, which is already in 9.
The patch for JDK 10 applies cleanly to JDK 9 and it should be fairly
low risk.
https://bugs.openjdk.java.net/browse/JDK-8181419
I've added a comment as to why I believe this bug should go into 9. It
also has the 'jdk9-fix-request' label.
Thanks,
Severin
--- Begin Message ---
2017/6/18 12:58:46 -0700, [email protected]:
> Per the JDK 9 schedule [1] we are now approaching the Initial Release
> Candidate milestone. After this week's build, which will be promoted
> on Thursday (2017/6/22), we should fix only those bugs that are truly
> showstoppers to the success of the release. I propose that we further
> tighten the goals previously adopted for RDP 2:
>
> - Fix all P1 bugs that are new in JDK 9 and critical to the success
> of this release;
>
> - Decommit from fixing any P1 bugs that are not new in JDK 9 and are
> not critical to this release, but were previously targeted to this
> release; and
>
> - Explicitly defer any P1 bugs that are new in JDK 9 but are either
> not critical to this release or cannot, for good reason, be fixed
> in this release.
>
> All P2-P5 bugs must be left to future releases, regardless of whether
> they are in product code, tests, or documentation. There is no need
> to defer unfixed P2-P5 bugs explicitly.
>
> The current list of RC bugs can be found here: http://j.mp/jdk9-rc .
>
> ...
Hearing no objections, I've documented the Release-Candidate Phase [2]
under the JDK 9 Project page [1]. I've also updated the status section
and the quick links on the latter.
- Mark
[1] http://openjdk.java.net/projects/jdk9/
[2] http://openjdk.java.net/projects/jdk9/rc
--- End Message ---
