JDK 11 is now in Rampdown Phase Two

[Sean Mullan]

> On Jul 30, 2018, at 5:31 PM, David Holmes <david.holmes at oracle.com> wrote:
> 
>> On 31/07/2018 2: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
> 
> Hmmm, that seems unnecessary overhead. In RDP2 P1 and P2 are required to be fixed, so requesting approval to do something required to be done, seems counter productive.

But why even have a fix request process then? I think the approval process is designed to add extra scrutiny on each fix as we get closer to GA regardless of the bug priority. 
> 
> But I agree the table and the later text seem at odds.

Yes, agreed. 

—Sean

> 
> David
> 
>> --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
>>>