openshift-docs
openshift-docs copied to clipboard
OSSM-6457 OSSM 2.6.0 (At Stage): [DOC] Release Notes, Known Issues an…
OSSM-6457 OSSM 2.6.0 (At Stage): [DOC] Release Notes, Known Issues and Bug Fixes
Version(s): 4.12+
Issue: https://issues.redhat.com/browse/OSSM-6457
Link to docs preview:
2.6: https://77982--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes.html
2.5.3: https://77982--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes.html#new-features-ossm-2-5-3
2.4.9: https://77982--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes.html#new-features-ossm-2-4-9
Fixed Issues: https://77982--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes.html#ossm-rn-fixed-issues-ossm_ossm-release-notes
QE review:
- [ ] QE has approved this change.
Additional information:
🤖 Wed Aug 07 14:40:04 - Prow CI generated the docs preview: https://77982--ocpdocs-pr.netlify.app Complete list of updated preview URLs: artifacts/updated_preview_urls.txt
/label peer-review-needed
For this round, only need to review the "New Features" section for 2.6, and the "Fixed issues" section.
/label peer-review-in-progress /remove-label peer-review-needed
/label peer-review-done /remove-label peer-review-in-progress
LGTM..!
/label peer-review-needed
Peer Review Round 2. The Component tables for 2.6, 2.5.3, and 2.4.9 have been updated, and QE has reviewed/approved this PR. You do not need to review all of the content as that was done in Round 1, but I also have no objection if you want to review all of the content of this PR. There is probably something to fix! ;) Thanks!
08/01/2024: Manual tests on OCP 4.12, 4.13, 4.14 returned 0 confilcts.
/retest
/retest
/retest
Rebase 08/06/2024
Manually checked against 4.12, 4.13, and 4.14 on 08/06/2024.
No conflicts reported.
Rebased against "main" 08/07/2024
@gwynnemonahan: all tests passed!
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
/label merge-review-needed
/cherrypick enterprise-4.17
/cherrypick enterprise-4.16
/cherrypick enterprise-4.15
/cherrypick enterprise-4.14
/cherrypick enterprise-4.13
/cherrypick enterprise-4.12
@adellape: new pull request created: #80157
In response to this:
/cherrypick enterprise-4.17
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@adellape: new pull request created: #80158
In response to this:
/cherrypick enterprise-4.16
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@adellape: new pull request created: #80159
In response to this:
/cherrypick enterprise-4.15
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@adellape: new pull request created: #80160
In response to this:
/cherrypick enterprise-4.13
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@adellape: new pull request created: #80161
In response to this:
/cherrypick enterprise-4.14
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@adellape: new pull request created: #80162
In response to this:
/cherrypick enterprise-4.12
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.