01/31/2025: So as not to confuse IA work with content that will go out with OSSM 3.0.0, this Epic has been created for OSSM 3.0.0 Rel Notes: https://issues.redhat.com/browse/OSSM-8765 . It contains issues and a link to the Jira filter used to capture any Jiras with the "Release Notes" box checked and the "Release Notes Text" box filled out. It is set as a Blocker for the Engineering OSSM 3.0.0 GA Release Epic: https://issues.redhat.com/browse/OSSM-8467 

If it turns out this Jira can be used instead, things can be consolidated accordingly. Right now, there are a lot of moving parts and an influx IA, the concern of bug fixes, known issues, etc. being missed that directly impact users is high, so OSSM-8765 has been created to specifically capture that content.

Service Mesh 3.0 should include a skeleton release notes page for GA. This will give us an opportunity to test drive a new format before 3.0 GA, as well as a place to document 3.0 Tech Preview release notes.

As discussed in the past, we should look at a different format that consolidates all of the information from a given release under a single heading, similar to how Serverless, Pipelines and GitOps structure their release notes:

• https://docs.openshift.com/serverless/1.32/about/serverless-release-notes.html
• https://docs.openshift.com/gitops/1.12/release_notes/gitops-release-notes.html
• https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html

The above are just possibilities, and we should design a page that will work best for service mesh's unique challenges.

We will need a component version support matrix similar to the one in Pipelines, though it will probably be simpler. Each OSSM 3.x operator version will map to a set of Istio and Kiali versions...and OCP versions. 

We will need a feature support table, similar to the one in Serverless' release note page, but given the breadth of service mesh, it may be better to document that on a separate page.

CC gmonahan rhn-support-tokeefe Not sure if there was an issue for this in 3.0, but I couldn't find one, so wanted to created it.

Potential content:

• This is issue identifying potential problems running 2.x and 3.x side by side will likely result in release notes: https://issues.redhat.com/browse/OSSM-8701