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

[Igor Ignatyev]

On Mon, 6 Jul 2020 21:34:56 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:

>> src/next.md line 73:
>> 
>>> 72: In this example, `MyTest.java` is ProblemListed on windows, tracked by bug `JDK-4711`.
>>> 73:
>>> 74: Currently there's [no support for multiple lines for the same
>>> test](https://bugs.openjdk.java.net/browse/CODETOOLS-7902481). For this reason it's important to always make sure
>>> there's no existing entry for the test before adding a new one, as multiple entries might lead to unexpected results,
>>> e.g.
>> 
>> Not sure where in this review to insert this but there is a sensible policy that you should make sure the bug report is
>> open. If you are submitting it that is easy to ensure but there have been cases where bugs are closed (without
>> necessarily being fixed) and the issue remains PL'd. A legitimate case where this occurs if a bug is fixed in one line
>> of development but the fix is not (yet:?) backported and I'm not sure how the "sensible policy" accounts for that.
>
> This is a very good point. I'm not sure how to express it though since this is meant to be a document for everyone, not
> only Oracle developers.
> I'm not sure what you mean with regards to the backport. If a fix is made in mainline it's removed from the ProblemList
> in mainline. The backport should remove it from the ProblemList in the update release once it's pushed there. The one
> thing that could be problematic is the `problemlist` label since that is only supposed to be on the main bug. But on
> the other hand I don't think there is any automation that looks at the ProblemLists in the update trains so having the
> label tied to the mainline issue won't be a problem in practice I think.

I think Phil is talking about a separate line of development of current feature release, i.e. `jdk/jdk` vs
`jdk/client`, and not about `jdk/jdk` vs `11u`. let's say you have fixed `JDK-4711` in `jdk/client` repo, but your fix
hasn't been propagated to `jdk/jdk` yet, and folks in `jdk/jdk` are still affected by `JDK-4711` and see test failures
(from non-problem-listed tests), so they want to go and problem-list them, but JBS says that `JDK-4711` is already
closed.

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

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