RFR: 8254146: Avoid unnecessary volatile write on new AtomicBoolean(false)

[Christoph Dreis]

On Wed, 7 Oct 2020 14:58:10 GMT, Claes Redestad <redestad at openjdk.org> wrote:

>> Marked as reviewed by rriggs (Reviewer).
>
>> @AlanBateman What would be the label (or workflow) for that now?
> 
> @dreis2211 what Alan reminded us of here is that all of j.u.concurrent is maintained upstream from the OpenJDK, and
> that this change needs to be coordinated with the maintainers there. Either by getting an OK to go ahead and push this
> as-is, or by contributing this patch to the JSR166 repo directly (which will then be integrated back into the OpenJDK
> at some point). See http://gee.cs.oswego.edu/dl/concurrency-interest/   This isn't anything new since the GitHub
> migration: Various bits and pieces of the OpenJDK sources are maintained upstream, and it's not always easy to igure
> out exactly where or how to go about upstreaming a change.

@cl4es Thanks. My question was more referring to how the PR tooling should be used these days to notify the
maintainers. As JSR166 is a crucial piece of the JDK I was wondering if there might be a way already via a label or
something. Or if this needs some good old mail (to concurrency-interest at cs.oswego.edu I suppose?)

-------------

PR: https://git.openjdk.java.net/jdk/pull/510