Skip to content

Conversation

@jmagak
Copy link
Member

@jmagak jmagak commented Jan 24, 2025

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-5070

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Jan 24, 2025

@jmagak jmagak changed the title Add compatible matrix Add compatibility matrix Jan 24, 2025
@nickboldt
Copy link
Member

nickboldt commented Jan 27, 2025

Looks OK now at https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-875/rel-notes-rhdh/#compatibility-matrix

image

Though that first column is sorta redundant now as we're only talking about the current release version, rather than listing multiple versions.

You could replace the need to maintain this table entiurely with a link to the Supported Platforms table at https://access.redhat.com/support/policy/updates/developerhub

But if @reestr and @christophe-f are happy with this duplication, then so am I.

@linfraze
Copy link
Member

linfraze commented Jan 27, 2025

I like the idea of linking to the the Supported Platforms table as the single source of truth, as @nickboldt suggested. Then we don't have to worry about duplicating existing information, maintaining multiple sources, or staying in sync. But if there is a reason why it makes sense to embed the duplicate info directly in the RNs, then we can do the needful.

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.

I can see the importance of displaying the compatibility details prominently in the Release Notes for each release but would either linking to the Supported Platforms page or just having a bulleted list of platforms look better than the table which seems overkill to me with just one row containing multiple data fields?

@Gerry-Forde
Copy link
Member

@jmagak For some reason, this link to the Compatibility Matrix links to a PR, can you review this please:
Screenshot 2025-01-27 at 17 47 01

@nickboldt
Copy link
Member

nickboldt commented Jan 27, 2025

having a bulleted list of platforms

... which you would then have to update every quarter if new platforms/versions are added.

https://access.redhat.com/support/policy/updates/developerhub is already a list... inside a table.

@Gerry-Forde in your screenshot above, where does the link for the Compatibility Matrix go? If we're talking about replacing that page with a link to https://access.redhat.com/support/policy/updates/developerhub then "Additional Resources" becomes a page with the same link on it. Why make people click several times for the same information?

Copy link
Member

@hmanwani-rh hmanwani-rh left a comment

Choose a reason for hiding this comment

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

@jmagak I’ve added a few minor comments. However, I recall that we planned to include a table for the supported versions in the release notes. For example, the 1.5 release notes would exclude version 1.3 and only include 1.5 and 1.4, which I think we can maintain indicating the relevant supported versions in a release. Additionally, how about we share the lifecycle page link in the "Additional Resources" section, similar to how it’s done in the "Supported Platforms" section?

Let me know your thoughts!

@jmagak jmagak force-pushed the RHIDP-5070-Compatibility-Matrix-in-RHDH-1.4 branch from 15041ab to 83a755f Compare January 28, 2025 09:29
@jmagak
Copy link
Member Author

jmagak commented Jan 28, 2025

@jmagak For some reason, this link to the Compatibility Matrix links to a PR, can you review this please: Screenshot 2025-01-27 at 17 47 01

@Gerry-Forde I have removed the link. It was intended to direct users to the Compatibility Matrix in the Release Notes for RHDH 1.4. Please assist me in reviewing the PR for the same.

@nickboldt
Copy link
Member

nickboldt commented Jan 28, 2025

Let me know your thoughts!

My $0.02 cents remains "why duplicate content when you can just link to the lifecycle page as the single source of truth?"

Also having 1.3 content in the 1.4 guide ... what value does that provide? is the idea to provide people with immediate access to seeing what has changed between 1.3 and 1.4 in terms of supported platforms/versions? If so that is again already in the lifecyle doc.

@hmanwani-rh
Copy link
Member

Let me know your thoughts!

My $0.02 cents remains "why duplicate content when you can just link to the lifecycle page as the single source of truth?"

Also having 1.3 content in the 1.4 guide ... what value does that provide? is the idea to provide people with immediate access to seeing what has changed between 1.3 and 1.4 in terms of supported platforms/versions? If so that is again already in the lifecyle doc.

@nickboldt The Lifecycle page currently doesn’t include the compatible Backstage versions, which I think would be helpful to show in our documentation. What are your thoughts on this?
Additionally, we may also need to include the tested hyperscaler versions.

@nickboldt
Copy link
Member

nickboldt commented Jan 28, 2025

Backstage version is already documented in https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.4/titles/rel-notes-rhdh/title-rhdh-release-notes.adoc

If you want to make it more obvious, how about this change to the copy so that the reader doesn't have to read "Developer Hub" 4 times (only twice) ?

#886

right above the matrix table :D

image

@nickboldt
Copy link
Member

we may also need to include the tested hyperscaler versions

Sounds like something to add for 1.5. We don't have it for 1.2-1.4, so why not add this New Feature in the upcoming release instead of the maintenance ones?

@jmagak
Copy link
Member Author

jmagak commented Jan 29, 2025

Instead of a Compatibility Matrix, we are adding an Additional Resources section that directs users to the lifecycle page. Hence, we are closing this PR.

@jmagak jmagak closed this Jan 29, 2025
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.

9 participants