Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: release notes for 1.4.1 (replace custom/manual content with JIRA-driven RN content too) #848

Open
wants to merge 4 commits into
base: release-1.4
Choose a base branch
from

Conversation

nickboldt
Copy link
Member

@nickboldt nickboldt commented Jan 14, 2025

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:

  • Code produced is complete
  • Code builds without errors
  • Tests are covering the bugfix
  • Relevant user documentation updated
  • Relevant contributing documentation updated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Jan 14, 2025

@@ -4,21 +4,28 @@

This section lists known issues in {product} {product-version}.

[id="known-issue-rhidp-3396"]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reordered content to be in number-sorted

You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/administration_guide_for_red_hat_developer_hub/index#proc-rhdh-deployment-config_assembly-admin-templates[Persistent Volume Claim (PVC)].
You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html-single/configuring/index#configuring-the-deployment[Persistent Volume Claim (PVC)].
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed link to 1.4 docs

You can now install third-party plugins in {product} without rebuilding the {product-very-short} application.

For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/introduction_to_plugins/index[Third party plugins].
== Ability to install third-party plugins in RHDH
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consumed from JIRA so better to use RHDH than the attribute here

See: link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview support scope].
====

[id="technology-preview-rhidp-5545"]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

manually added content replaced by jira-derived RN content

@@ -14,40 +14,39 @@
set -e

# get the z-stream version from the bundle-version attribute. Note that while chart-version could be larger, this is the correct value for CVE tracking
product_version="$(grep ':product-bundle-version:' artifacts/attributes.adoc | cut -d' ' -f2 )"
Copy link
Member Author

@nickboldt nickboldt Jan 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated script from updates done for 1.3.3, ported here.

@@ -13,7 +13,7 @@ sections:
AND status in (Closed, "Release Pending")
AND "Release Note Type" in ("Feature", "Enhancement")
AND fixVersion >= "{version_minor}"
AND fixVersion <= "{version_patch}"
AND fixVersion < "{version_next}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is better so that we don't have to move things to an arbitrary 1.4.z version for Known Issues

[NOTE]
====
In addition to the previously provided tables, you can compare the link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.4/modules/dynamic-plugins/rhdh-supported-plugins.csv[RHDH 1.4 CSV file] with the link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.3/modules/dynamic-plugins/rhdh-supported-plugins.csv[RHDH 1.3 CSV file] to identify the changes in dynamic plugins.
[id="removed-functionality-rhidp-4853"]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the breaking change section is driven by JIRA Release Notes Type = "Removed Functionality", not "Feature"

@nickboldt nickboldt changed the title chore: release notes for 1.4.1 (removing... chore: release notes for 1.4.1 (replace custom/manual content with JIRA-driven RN content too) Jan 14, 2025
@nickboldt nickboldt marked this pull request as draft January 14, 2025 20:09
@nickboldt nickboldt marked this pull request as ready for review January 15, 2025 15:48
Copy link
Member

@Gerry-Forde Gerry-Forde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nickboldt I've reviewed this content and left some suggestions.

@nickboldt
Copy link
Member Author

Changes applied in the python script to add back the empty lines, and applied all your RN copy changes in the JIRAs where the content comes from.

In future please make edits in JIRA since that is the singel source of truth for RN content.

LMK if I missed anything or if the update is ready to merge. Thanks!

@themr0c
Copy link
Member

themr0c commented Jan 16, 2025

Awesome! Thank you!

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]>
@nickboldt
Copy link
Member Author

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]>
Comment on lines +10 to +20
=== Updating Channel does not trigger an Operator Update

Administrators may encounter problems updating {product-short} across channels. As a workaround, to upgrade across channels:

* Delete the {product-very-short} operator subscription (but not its operands)
* Create a new subscription pointing to the new channel (`fast` or `fast-1.4`), using the latest CSV
* Once installed, any existing Backstage objects will be upgraded through the new operator

Note, your app config may need to be adjusted as part of the rollout, if plugins have changed their name or configuration requirements. See link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html-single/release_notes/index#feature-rhidp-4853[Plugins with updated scope].


Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
=== Updating Channel does not trigger an Operator Update
Administrators may encounter problems updating {product-short} across channels. As a workaround, to upgrade across channels:
* Delete the {product-very-short} operator subscription (but not its operands)
* Create a new subscription pointing to the new channel (`fast` or `fast-1.4`), using the latest CSV
* Once installed, any existing Backstage objects will be upgraded through the new operator
Note, your app config may need to be adjusted as part of the rollout, if plugins have changed their name or configuration requirements. See link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html-single/release_notes/index#feature-rhidp-4853[Plugins with updated scope].
=== Updating Channel does not trigger an Operator update
Administrators may encounter problems updating {product-short} across channels. As a workaround, to upgrade across channels:
* Delete the {product-very-short} Operator subscription. Do not delete the operands.
* Create a new subscription pointing to the new channel (`fast` or `fast-1.4`), using the latest CSV.
* When you install the new operator, the existing Backstage objects will be upgraded.
[NOTE]
If plugin names or configuration requirements have been changed, you may need to update your application configuration. See link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html-single/release_notes/index#feature-rhidp-4853[Plugins with updated scope].

I realize that this content is taken directly from the associated Jira, so I've edited the Jira RN Text to mirror this suggestion .

[id="bug-fix-rhidp-5308"]
=== notification backend and catalog backend gitlab org failing to load with MODULE_NOT_FOUND

In the previous version of {product-short}, the gitlab org catalog backend plugin and notification backend plugin would fail to load when configured with a `MODULE_NOT_FOUND` error. This has been fixed by embedding the missing dependencies in the dynamic plugins.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In the previous version of {product-short}, the gitlab org catalog backend plugin and notification backend plugin would fail to load when configured with a `MODULE_NOT_FOUND` error. This has been fixed by embedding the missing dependencies in the dynamic plugins.
In the previous version of {product-short}, the GitLab Org catalog backend plugin (`plugin-catalog-backend-module-gitlab-org`)and the Notification backend plugin (`plugin-notifications-backend`) fail to load when configured with a `MODULE_NOT_FOUND` error. This has been fixed by embedding the missing dependencies in the dynamic plugins.

This suggestion has also been updated in the Jira RN Text field.

Copy link
Member

@Gerry-Forde Gerry-Forde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nickboldt I've reviewed your latest commit changes and left a couple of suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants