RFR: Using backports for stabilization repositories

[David Holmes]

On Wed, 31 May 2023 18:34:03 GMT, Erik Helin <ehelin at openjdk.org> wrote:

> Hi all,
> 
> please review this patch that replaces the documentation on the "forward ports" process with the [recently adopted](https://mail.openjdk.org/pipermail/jdk-dev/2023-May/007889.html) "backports" process. The changes are fairly small since the guide already contains great documentation on backports, I just had to adopt it slightly to also cover stabilization repositories.
> 
> Thanks!
> Erik

There are a couple of things that are unclear me and I'm not sure where they should be addressed:

1. When backporting to the release stabilization repository, as opposed to an update release repository, there is no specific backport approval process, but a particular issue may need specific approval due to the nature of the issue and which stage of rampdown we are in (e.g. late enhancements).

2. If we have a candidate issue for the release stabilization repo, which we will have to push to mainline first, should we be marking the JBS issue somehow to show that the backport is intended to be done? With the old system we would keep an issue targeted to the older release in general and the forward-port would create the backport issue for the new release. With the new scheme the JBS issue should be targeted to the latest release and so you can't tell by looking at that if there is any intent to backport it.

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

PR Review: https://git.openjdk.org/guide/pull/105#pullrequestreview-1471211660