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

[Jesper Wilhelmsson]

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

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

Ah, of course. There is no implemented solution for that right now. Two fairly easy options would be 1, Merge client
into mainline, or 2, use a different fix version for client like done for project repos. This is something that we
should bring up in a different thread with a different audience.

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

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