RFR: Filing bug, ProblemListing, Backing out [v2]

Jesper Wilhelmsson jwilhelm at openjdk.java.net
Fri Jul 10 00:17:04 UTC 2020


On Mon, 6 Jul 2020 22:44:40 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:

>> AFAIK, The verification process isn't part of any OpenJDK process and is used/done mainly internally by Oracle. why do
>> you think that verification status should be set for all backed out issues?
>
> The text is based on an ancient definition of how to back out changes. That text was JDK wide (not only HotSpot) but
> yes, internal to Oracle. If verification is not important or done for all issues I'd be happy to remove that sentence.

There has been a longer discussion in the email thread on guide-dev that for some reason hasn't been copied here. From
that and other discussions I now have a directive on this issue; The verification field is both useful and used, also
for non-Oracle issues. It's not an Oracle internal field and anyone in the community can use it - it's actually
documented on the OpenJDK wiki even though it's not always easy to find information in a wiki. For this reason it's
actually even more important to clarify how it's intended to be used in the cases where we use it. Therefore we should
include the verification part in this description as it is part of the process.

As for using "Fix failed"; this was very well explained by Igor in the same mail thread: this is the value that means
that the bug still exists - and it does since the fix was backed out. It doesn't mean that the fix itself was bad or
broken.

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

PR: https://git.openjdk.java.net/guide/pull/21


More information about the guide-dev mailing list