[11u] RFR 8235183: Remove the "HACK CODE" in comment
Andrew Haley
aph at redhat.com
Fri Mar 13 10:02:23 UTC 2020
Hi,
On 3/13/20 9:44 AM, Langer, Christoph wrote:
>> -----Original Message-----
>> From: jdk-updates-dev <jdk-updates-dev-bounces at openjdk.java.net> On
>> Behalf Of Andrew Haley
>> Sent: Freitag, 13. März 2020 10:30
>> To: Reingruber, Richard <richard.reingruber at sap.com>; jdk-updates-
>> dev at openjdk.java.net
>> Subject: Re: [11u] RFR 8235183: Remove the "HACK CODE" in comment
>>
>> On 3/12/20 2:51 PM, Reingruber, Richard wrote:
>>>
>>> 11u webrev:
>>> http://cr.openjdk.java.net/~rrich/webrevs/8235183.jdk11u/webrev.0/
>>>
>>> Testing: nightly tests @SAP, i.e. jck and jtreg, also in Xcomp mode with
>> fastdebug and release
>>> builds on all platforms.
>>
>> This isn't suitable for a backport. It fixes no bugs, and has no
>> user-visible behaviour.
>
> Well, one could certainly see it that way. However, we always tried
> to backport what we found was backported to the equivalent Oracle
> release.
How do you know? Presumably because you have access to Oracle's closed
source code.
> Shall we change this policy?
That policy exists because we don't want to have bugs in OpenJDK which
are fixed in Oracle's releases. There never has been any policy which
says that the source code should be identical, and that's impossible
anyway. It never occurred to me that anyone would interpret the policy
in such a way.
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the jdk-updates-dev
mailing list