JDK 11 is now in Rampdown Phase Two (original) (raw)
Phil Race philip.race at oracle.com
Mon Jul 30 17:17:02 UTC 2018
- Previous message: JDK 11 is now in Rampdown Phase Two
- Next message: JDK 11 is now in Rampdown Phase Two
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think it should say that, for clarity and consistency. If you read the whole document, it is covered.
Fix: If the bug is current then develop a fix and either integrate it when ready (in RDP 1 or request approval to integrate it via the fix-request process (RDP 2 and RC) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It appears one fix was pushed 7/27 without following this process which has been in effect since 7/26.
-phil.
On 07/30/2018 09:47 AM, Sean Mullan wrote:
For RDP 2, it is my understanding that any P1-P2 bugs that are not test or doc issues now need approval (according to the Fix-Request Process of JEP 3) before you can push. Is that correct? If so, I think the Fix column of the table at the beginning of JEP 3 should say:
Current P1–P2, with approval --Sean On 7/26/18 5:19 PM, mark.reinhold at oracle.com wrote: Per the JDK 11 schedule [1], we are now in Rampdown Phase Two.
The overall feature set is frozen. No further JEPs will be targeted to this release. Per the JDK Release Process [3] we now turn our focus to P1 and P2 bugs. Late enhancements are still possible with approval, but the bar is now extraordinarily high. If you’re responsible for any of the bugs on the RDP 2 candidate-bug list [3] then please see JEP 3 for guidance on how to handle them. - Mark
[1] http://openjdk.java.net/projects/jdk/11/#Schedule [2] http://openjdk.java.net/jeps/3 [3] http://j.mp/jdk-rdp-2
- Previous message: JDK 11 is now in Rampdown Phase Two
- Next message: JDK 11 is now in Rampdown Phase Two
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]