chore: release notes for 1.4.1 (replace custom/manual content with JIRA-driven RN content too) #848
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-848/ @ 01/20/25 12:02:42 |
nickboldt
commented
Jan 14, 2025
nickboldt
commented
Jan 14, 2025
nickboldt
commented
Jan 14, 2025
nickboldt
commented
Jan 14, 2025
nickboldt
commented
Jan 14, 2025
nickboldt
commented
Jan 14, 2025
modules/release-notes/single-source-release-notes-template.adoc.jinja
Outdated
Show resolved
Hide resolved
nickboldt
commented
Jan 14, 2025
nickboldt
commented
Jan 14, 2025
nickboldt
changed the title
nickboldt
added
Peer review needed 📖
SME review needed 🔩
and removed
SME review done ⛅
Peer review done 📘
labels
Signed-off-by: Nick Boldt <[email protected]> fix queries Signed-off-by: Nick Boldt <[email protected]> put content in JIRA instead of overriding content after generation Signed-off-by: Nick Boldt <[email protected]> put back deleted content (why do people keep forgetting to put RN content in JIRA?) Signed-off-by: Nick Boldt <[email protected]> regen from jira Signed-off-by: Nick Boldt <[email protected]> regen more Signed-off-by: Nick Boldt <[email protected]> Remove empty lines Signed-off-by: Nick Boldt <[email protected]>
Signed-off-by: Nick Boldt <[email protected]> add CVE-2024-56334 to snip-fixed-security-issues-in-product-1.4.1.adoc Signed-off-by: Nick Boldt <[email protected]> add spaces back into the generated RN Signed-off-by: Nick Boldt <[email protected]> more fixes from JIRA updates Signed-off-by: Nick Boldt <[email protected]>
|
Added 3 missing RN items that were fixed in this release but which didn't have the Release Note Status = Done. |
…use Release Note Status was not set to Done Signed-off-by: Nick Boldt <[email protected]> remove dupe RN issue (https://issues.redhat.com/browse/RHIDP-5319 is a subset of https://issues.redhat.com/browse/RHIDP-5308; some reformatting and language cleanup Signed-off-by: Nick Boldt <[email protected]>
Gerry-Forde
reviewed
Jan 19, 2025
Gerry-Forde
reviewed
Jan 19, 2025
Gerry-Forde
reviewed
Jan 19, 2025
There was a problem hiding this comment.
@nickboldt I've reviewed your latest commit changes and left a couple of suggestions.
Signed-off-by: Nick Boldt <[email protected]>
Gerry-Forde
added
Peer review done 📘
and removed
Peer review needed 📖
SME review needed 🔩
labels
Gerry-Forde
approved these changes
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
chore: release notes for 1.4.1 (replace custom/manual content with JIRA-driven RN content too)
Signed-off-by: Nick Boldt [email protected]
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
https://issues.redhat.com/browse/RHIDP-5521
https://issues.redhat.com/browse/RHIDP-5525
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:
Reviewers
Reviewers, please comment how you tested the PR when approving it.