[14] JDK-8225130 question

[Rob McKenna]

Sibabrata (cc'd) has pushed that fix to the CPU repo after it was
approved via the cpu fix approval process. (i.e. the approval process
that applies to all CPU content)

You are correct however, the fix should have been pushed via the open
repo. In order to avoid this issue in that repo I have approved the
14u fix request.

I think it would make sense for Sibabrata or I to push that changeset to
the open repo if you have no objections.

    -Rob

On 03/03/20 17:51, Aleksey Shipilev wrote:
> Hi,
> 
> Today, I had requested 14u backport for:
>   https://bugs.openjdk.java.net/browse/JDK-8225130
> 
> ...and got jdk14u-fix-yes. Imagine my surprise when I saw the 14.0.2 backport already done today:
>   https://bugs.openjdk.java.net/browse/JDK-8240369
> 
> That's odd, but somewhat understandable.
> 
> Yet, there are *no* changesets in public repositories!
>   https://hg.openjdk.java.net/jdk-updates/jdk14u/log?rev=8225130
>   https://hg.openjdk.java.net/jdk-updates/jdk14u/log?rev=8240369
> 
> What gives? Is there some private jdk14u fork that hgupdater work on? Are Oracle committers push to
> 14u without following the Update Releases process?
> 
> -- 
> Thanks,
> -Aleksey
>