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

[Jesper Wilhelmsson]

On Mon, 6 Jul 2020 22:31:58 GMT, Igor Ignatyev <iignatyev at openjdk.org> wrote:

>> I guess this is a question for those who normally handle fix verification and may have scripts that look for different
>> verifications.
>> There's only four values to choose from: "None", "Verified", "Not verified", and "Fix failed".
>> "Verified" means that the fix solved the problem and no more action is required, so this is clearly not right. "Not
>> verified" seems wrong since it actually was verified that the fix caused problems - or it wouldn't need to be backed
>> out. "None" could be used in my mind, but I can imagine that there are filters that treats "None" as issues that needs
>> verification. So changing to using this would probably cause problems. That leaves "Fix failed".  Maybe Joe knows why
>> this was designed as it is?  Anyhow, it is the current process and we need to bring it up with the right people before
>> changing it.
>
> 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.

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

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