Fix release notes links

[jmagak]

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): 1.4

Add the relevant labels to the Pull Request.
Issue: https://issues.redhat.com/browse/RHIDP-5458

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-843/ @ 01/27/25 12:27:32

[linfraze]

A couple comments, otherwise lgtm

[linfraze]

approving /lgtm

[nickboldt]

approving /lgtm

release notes are generated using JIRA as the single source of truth. Please apply your changes in https://issues.redhat.com/browse/RHIDP-3621 then run this script:

https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.4/modules/release-notes/single-source-release-notes.py

If you apply these changes and then we release a 1.4.2 security / bug fix update, your changes will be overwritten by the above script.

So it's 100% better to use JIRA release note text fields for the contents of the release notes.

[nickboldt]

Regenerated from JIRA release note text fields and pushed the changes into your PR.

If that reverted your requested changes, please apply them in JIRA and I can re-run the ./modules/release-notes/single-source-release-notes.py script for you.

Here's my changes (with whitespace / line ending changes ignored):

6bc66e9?w=1

[jmagak]

Regenerated from JIRA release note text fields and pushed the changes into your PR.

If that reverted your requested changes, please apply them in JIRA and I can re-run the ./modules/release-notes/single-source-release-notes.py script for you.

Here's my changes (with whitespace / line ending changes ignored):

6bc66e9?w=1

Hi @nickboldt , I ran the script and this PR should be in sync with those from your end.

[jmagak]

@rm3l @nickboldt @jmagak @Preeticp even more than a link to a page about what configuration profiles are, what I think would be most helpful for the user is to know what the additional profiles are, why they have been added, and how the user can benefit from the addition. Any reason why we aren't sharing that info?

That is a great suggestion, as well as wonderful questions you have raised, @linfraze . I trust that a summary of the content in the link, rather than linking the entire document, might suffice in this case. My question, however, is where to draw the line on what to highlight from the upstream document, especially if we want to avoid leaving the user searching for additional content from where they cannot access.

[nickboldt]

RN status for https://issues.redhat.com/browse/RHIDP-4780 should be changed to exclude this item from the RN regeneration script at https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.4/modules/release-notes/single-source-release-notes.py

[nickboldt]

I notice you removed https://issues.redhat.com//browse/RHIDP-3817 as it's now set as upstream only. 👍