Only P1-P3 bugs fixes are allowed to push into jdk9 now

Vladimir Kozlov vladimir.kozlov at oracle.com
Thu Jan 12 19:54:21 UTC 2017


Hi Volker,

The general internal Oracle consensus after discussions was that we may 
allow only very small high priority RFEs for external ports code. It 
should use FC extension process we used before (labels and request 
comments) and approved case by case. And this is for limited time only - 
we all want to have jdk 9 stable on all platforms when it is released as 
Andrew said.

And definitely not if changes touch a common code. If you need then 
split it into separate changes as bug if possible - I assume you can 
have cases when you need to add #ifdef into existing tests, for example.

Also I would like again to enforce priority limit to P1-P3. If you think 
a fix should go into jdk 9 it should have high priority. Otherwise it 
can wait jdk 10.

Regards,
Vladimir

On 1/4/17 11:30 AM, Vladimir Kozlov wrote:
> On 1/4/17 2:23 AM, Volker Simonis wrote:
>> On Tue, Jan 3, 2017 at 7:53 PM, Vladimir Kozlov
>> <vladimir.kozlov at oracle.com> wrote:
>>> We are currently in "Rampdown" phase for jdk 9 which allows only
>>> P1-P3 bugs
>>> fixes. Note for Hotspot it started week ago.
>>>
>>> http://openjdk.java.net/projects/jdk9/
>>>
>>> Please, make sure bugs you are planning to fix have P1-P3 priority
>>> and "fix
>>> version" is jdk 9. I just updated JDK-8171266 [1] for that.
>>>
>>
>> Thanks a lot Vladimir. I'll push it today.
>>
>> Just for clarification: do the "Rampdown phase rules" also apply to
>> non-Oracle platforms like ppc64 or s390x? In the past, we were allowed
>> to push non P1-P3 bugs or enhancements even in later phases as long as
>> they didn't touch shared code. Is this still allowed or do we now have
>> to strictly conform to the process even for ppc64/s390x-only changes?
>
> JDK 9 schedule was approved by all, including Java Community outside
> Oracle.
>
> I looked on original Mark's email about "JDK 9 Rampdown Phase 1" and
> there were no exceptions listed:
>
> http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-August/004777.html
>
> But I understand that JDK 9 schedule reflects the process inside Oracle
> and may not be applied directly to your process.
> I will try to clarify situation with your ports regarding JDK 9 schedule
> and inform you.
>
> Regards,
> Vladimir
>
>>
>> Thanks a lot and best regards,
>> Volker
>>
>>> You can rise priority to P3 if you think a bug must be fixed in jdk 9 or
>>> defer it to jdk 10 - set "fix version" to 10.
>>>
>>> I see 3 aarch64 P4-P5 bugs which should be updated accordingly:
>>>
>>> https://bugs.openjdk.java.net/browse/JDK-8170101
>>> https://bugs.openjdk.java.net/browse/JDK-8170103
>>> https://bugs.openjdk.java.net/browse/JDK-8165058
>>>
>>> Thanks,
>>> Vladimir
>>>
>>> [1] https://bugs.openjdk.java.net/browse/JDK-8171266
>>> "PPC64: Add support to -XX:RTMSpinLoopCount=0"
>>>


More information about the ppc-aix-port-dev mailing list