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

[Joe Darcy]

Hello,

Reply interspersed below...

On 7/6/2020 3:28 PM, Jesper Wilhelmsson wrote:
> On Mon, 6 Jul 2020 20:09:30 GMT, Phil Race <prr at openjdk.org> wrote:
>
[snip]


> 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.

To condense a longer narrative, the verification field was added at the 
behest of Oracle's JDK SQE organization and that organization generally 
manages setting the field. The most typically outcome is "Verified" once 
the regression tests associated with a fix are seen to pass. In 
exceptional cases, there are conditions where a fix is marked as failed.

I suggesting focusing on other aspects of bug management besides 
verification.

HTH,

-Joe