cover the documentation linking options in release notes

[calnan]

added an explanation on the support of JavaDoc like links and the automatic linking of JBS IDs

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace

Reviewers

• Iris Clark (@irisclark - Reviewer) ⚠️ Review applies to f2737a69

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/guide.git pull/167/head:pull/167
$ git checkout pull/167

Update a local copy of the PR:
$ git checkout pull/167
$ git pull https://git.openjdk.org/guide.git pull/167/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 167

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/guide/pull/167.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back calnan! 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.

[openjdk]

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

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

cover the documentation linking options in release notes

Reviewed-by: iris

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 1 new commit pushed to the master branch:

• 82460a3: Minor spelling correction in guide

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@irisclark) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 05: Full - Incremental (5dfaf4bf)
• 04: Full - Incremental (a12cba2f)
• 03: Full - Incremental (f2737a69)
• 02: Full - Incremental (c8597bd8)
• 01: Full - Incremental (803195dc)
• 00: Full (8c8422da)

[openjdk]

⚠️ @calnan the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout releasse-note-links
$ git commit --author='Preferred Full Name <you@example.com>' --allow-empty -m 'Update full name'
$ git push

[calnan]

made the updates from the feedback. The JDK 26 EA notes are beginning to include notes that are using []'s:

https://jdk.java.net/26/release-notes

I'm going to leave this PR open for a few more weeks to capture and more clarifications needed as other notes are converted.