RFR: Clarifications on backport process

Sean Mullan mullan at openjdk.org
Mon Jul 3 14:01:26 UTC 2023


On Wed, 28 Jun 2023 15:33:57 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:

> More clarifications needed on the new "no forwardport" policy.

src/guide/backporting.md line 20:

> 18: ## Backporting to a feature release stabilization repository
> 19: 
> 20: During rampdown of a feature release there are two repositories in play, the release stabilization repository for the outgoing release, and the mainline repository where the next release is being developed. Any change going into the release stabilization repository is likely to be desired in mainline as well. When making a change intended both for the stabilization release and the mainline repository, you should always create your pull request targeting the mainline repository first, and then, once the pull request is integrated, backport the resulting commit to the release stabilization repository. For bugfixes that are **only** applicable to the release stablization repository, regular pull requests targeting the stabilization fork should be created.

I know you already integrated this, but I noticed a typo in the last sentence: s/stablization/stabilization

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

PR Review Comment: https://git.openjdk.org/guide/pull/108#discussion_r1250934488


More information about the guide-dev mailing list