8273732: Clarify review policies for clean backports in JavaFX update releases

[kevinrushforth]

Added a paragraph indicating that a review of a clean backport to an update release is optional, if the bug in question has been approved for inclusion into the release.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8273732: Clarify review policies for clean backports in JavaFX update releases

Reviewers

• Phil Race (@prrace - Reviewer)
• Pankaj Bansal (@pankaj-bansal - Committer)
• Johan Vos (@johanvos - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx17u pull/9/head:pull/9
$ git checkout pull/9

Update a local copy of the PR:
$ git checkout pull/9
$ git pull https://git.openjdk.java.net/jfx17u pull/9/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 9

View PR using the GUI difftool:
$ git pr show -t 9

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jfx17u/pull/9.diff

[bridgekeeper]

👋 Welcome back kcr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 01: Full - Incremental (af930d70)
• 00: Full (8bc1bc69)

[openjdk]

@kevinrushforth This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8273732: Clarify review policies for clean backports in JavaFX update releases

Reviewed-by: prr, pbansal, jvos

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 2 new commits pushed to the master branch:

• 2947986: 8272329: Cherry pick GTK WebKit 2.32.3 changes
• 5397290: 8270479: WebKit 612.1 build fails with Visual Studio 2017

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[johanvos]

This clarifies it indeed.

[kevinrushforth]

/integrate

[openjdk]

Going to push as commit 549bfef.
Since your change was applied there have been 2 commits pushed to the master branch:

• 2947986: 8272329: Cherry pick GTK WebKit 2.32.3 changes
• 5397290: 8270479: WebKit 612.1 build fails with Visual Studio 2017

Your commit was automatically rebased without conflicts.

[openjdk]

@kevinrushforth Pushed as commit 549bfef.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.