7265: Update Release Notes for 8.1.0

[thegreystone]

Updated for 8.1.0.

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7265: Update Release Notes for 8.1.0

Reviewers

• Jean-Philippe Bempel (@jpbempel - Committer) ⚠️ Review applies to c3fdaf4
• Guru Hb (@guruhb - Reviewer) ⚠️ Review applies to c3fdaf4

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 285

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

Using diff file

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

[thegreystone]

Let me know if I forgot something that should be mentioned.

[bridgekeeper]

👋 Welcome back hirt! 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 (2f7b44cb)
• 00: Full (c3fdaf41)

[openjdk]

@thegreystone 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:

7265: Update Release Notes for 8.1.0

Reviewed-by: jpbempel, ghb

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 30 new commits pushed to the master branch:

• eafd075: 7122: Rules evaluation never complete
• 68d5eec: 7369: Update THIRDPARTYREADME.TXT and its license attribute
• 76f5a56: 7348: JMC preference options are duplicated
• bba7e41: 7349: JFR Parser struct types hashcode is not stable
• fb71a22: 6817: AutoBoxing rule can crash due to null dereference
• ef886f3: 7358: Rename Agent Plug-in in the JVM Browser
• 4b492a4: 7362: Reference wrong in agent plug-in.xml
• 0113da9: 7353: JMC fails to build because it can't download babel dependency
• c54c00b: 6922: Reintroduce GC summary screen
• c6e0606: 4792: Stop using System.out/err.println and e.printStackTrace
• ... and 20 more: https://git.openjdk.java.net/jmc/compare/d622dd3fa3553885c6369c5c2937780cab21f0c5...master

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.

[thegreystone]

/reviewers 2

[openjdk]

@thegreystone
The number of required reviews for this PR is now set to 2 (with at least 1 of role committers).

[guruhb]

Looks good to me

[aptmac]

Shouldn't be an issue now after: eafd075

[thegreystone]

/integrate

[openjdk]

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

• eafd075: 7122: Rules evaluation never complete
• 68d5eec: 7369: Update THIRDPARTYREADME.TXT and its license attribute
• 76f5a56: 7348: JMC preference options are duplicated
• bba7e41: 7349: JFR Parser struct types hashcode is not stable
• fb71a22: 6817: AutoBoxing rule can crash due to null dereference
• ef886f3: 7358: Rename Agent Plug-in in the JVM Browser
• 4b492a4: 7362: Reference wrong in agent plug-in.xml
• 0113da9: 7353: JMC fails to build because it can't download babel dependency
• c54c00b: 6922: Reintroduce GC summary screen
• c6e0606: 4792: Stop using System.out/err.println and e.printStackTrace
• ... and 20 more: https://git.openjdk.java.net/jmc/compare/d622dd3fa3553885c6369c5c2937780cab21f0c5...master

Your commit was automatically rebased without conflicts.

[openjdk]

@thegreystone Pushed as commit f1cae17.

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