RFR: Section on backporting [v7]

[Jesper Wilhelmsson]

On Thu, 2 Dec 2021 23:26:38 GMT, Kevin Rushforth <kcr at openjdk.org> wrote:

> That violates our best practices of not reusing a bug. This would lead to two commits in the repo with the same bug ID and different content. There's a reason we don't ever do this in the mainline.

Right.. So what is the best solution here then?

1. Create the redo issue of type Bug and push it as a separate fix to 11u. Link the new issue with the old main issue as related. Pro: New bugid is a Bug. Cons: The old main issue won't show the new fix as a backport and won't have 11u in the list of backports.
2. Create the redo issue of type Bug and push it as a separate fix to 11u. Link the new issue as a backport of the old main issue. Pro: New bugid is a Bug, old main issue will show the new bug as a backport. Cons: Backport-link to an issue of type Bug.
3. Create the redo issue of type Backport and push it with the redo bugid. Pro: Everything will look good in JBS. Cons: Bugid in change history will refer to a backport issue.
4. Create a new mainline Bug issue and close it as duplicate of the old main issue. Create the redo issue as a backport of the duplicate and push with the duplicate bugid. Pro: Most things will probably look ok, won't break any rules I think. Cons: Seems like  a lot of process for the sake of process, not a very pragmatic solution.

I'd vote for #3 or some better solution not listed here.

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

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