-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Add OSSM Operator version to Release Notes
-
False
-
-
False
-
Release Notes
-
Release Notes
-
Done
-
0% To Do, 0% In Progress, 100% Done
-
Figure out best way to include this information for 2.6 Release Notes.
Raised by https://issues.redhat.com/browse/OSSM-5925
The release version is not always the same as the Service Mesh Operator version. This sometimes causes confusion for users when upgrading as it is unclear what Service Mesh Operator version is supported with each release. May also relate to https://issues.redhat.com/browse/OSSM-5318 and was previously raised and attempted to address by https://issues.redhat.com//browse/OSSM-3473
Suggested solution, per Slack thread from 02/14/2024 https://redhat-internal.slack.com/archives/C01R9E3SFEV/p1707921230860139 :
The operator can be mentioned only in the latest version but with info on which previous version it updates
New features Red Hat OpenShift Service Mesh version 2.5.0 ... The operator for this version (2.5.0) contains update 2.4.6 and 2.3.10 for previous SMCP release
—
Part of this stems from the structure of 2.x release notes. Each release has its own entry, but if a user looks at 2.4.5, it is not clear that 2.4.5 also included 2.3.x and 2.2.x. Something to keep in mind for 3.x.
- causes
-
OSSM-5925 ServiceMesh minor version upgrade path and channels not proper
-
- Closed
-