RFR: Backporting related changes

Tobias Hartmann thartmann at openjdk.org
Thu Jun 27 05:42:21 UTC 2024


On Wed, 26 Jun 2024 23:40:27 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:

> Added a section on backporting multiple related changes.
> Replaced "push" with "integrate" in several places since developers can't push to the OpenJDK repositories.
> Removed the JBS label vthreads that has been retired and is no longer in use in JBS.

src/guide/backporting.md line 32:

> 30: Testing each individual change is more likely to find issues than just testing the single merged change. It's also easier and less error prone to use the `/backport` command on each commit instead of manually cherrypick and deal with the merges etc.
> 31: 
> 32: And finally, if backporting each commit individually, the JBS records will clearly indicate that the followup changes has been backported as well. This is important as there is tooling that verifies that everything is done in the right way. That tooling will be confused if it can't deduct from JBS what has happened.

Suggestion:

And finally, if backporting each commit individually, the JBS records will clearly indicate that the followup changes have been backported as well. This is important as there is tooling that verifies that everything is done in the right way. That tooling will be confused if it can't deduct from JBS what has happened.

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

PR Review Comment: https://git.openjdk.org/guide/pull/129#discussion_r1656468149


More information about the guide-dev mailing list