OSDOCS-17313 [NETOBSERV] Refactor rel notes 1.6.1-1.6.2 #102457
Conversation
openshift-ci
bot
added
size/M
|
🤖 Thu Nov 13 21:28:04 - Prow CI generated the docs preview: |
gwynnemonahan
force-pushed
the
OSDOCS-17313
branch
3 times, most recently
from
84585cd to
c84ac25
Compare
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
lahinson
added
merge-review-in-progress
lahinson
left a comment
lahinson
left a comment
There was a problem hiding this comment.
I spotted 2 tiny things you might want to fix before I merge. Otherwise, LGTM!
modules/network-observability-operator-release-notes-1-6-1-fixed-issues.adoc
Outdated
Show resolved
Hide resolved
modules/network-observability-operator-release-notes-1-6-2-fixed-issues.adoc
Outdated
Show resolved
Hide resolved
gwynnemonahan
force-pushed
the
OSDOCS-17313
branch
from
af9e67c to
b638a07
Compare
lahinson
removed
the
merge-review-in-progress
|
@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. |
|
/cherrypick enterprise-4.12 |
|
/cherrypick enterprise-4.14 |
|
/cherrypick enterprise-4.15 |
|
/cherrypick enterprise-4.16 |
|
/cherrypick enterprise-4.17 |
|
@lahinson: new pull request created: #102511 In response to this:
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. |
|
@lahinson: new pull request created: #102512 In response to this:
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. |
|
@lahinson: new pull request created: #102513 In response to this:
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. |
|
/cherrypick enterprise-4.18 |
|
@lahinson: new pull request created: #102514 In response to this:
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. |
|
/cherrypick enterprise-4.19 |
|
/cherrypick enterprise-4.20 |
|
/cherrypick enterprise-4.21 |
|
@lahinson: new pull request created: #102515 In response to this:
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. |
|
@lahinson: new pull request created: #102516 In response to this:
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. |
|
@lahinson: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.16 from head openshift-cherrypick-robot:cherry-pick-102457-to-enterprise-4.16: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-102457-to-enterprise-4.16."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"} In response to this:
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. |
|
@lahinson: new pull request created: #102517 In response to this:
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. |
|
@lahinson: new pull request created: #102518 In response to this:
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. |
|
@lahinson: new pull request created: #102519 In response to this:
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. |
4 participants
OSDOCS-17313 [NETOBSERV] Refactor rel notes 1.6.1-1.6.2
Version(s):
4.12, 4.14+
Issue:
https://issues.redhat.com/browse/OSDOCS-17313
Link to docs preview:
QE review:
QE is not required for this PR. This PR modularizes Network Observability Operator release notes for 1.3.0 only. There are no content changes.
Additional information:
The Network Observability Operator release notes are being modularized through a series of PRs. This means that things will get cleaned up and consolidated along the way.
Some of these PRs may contain updates to previously merged content for the purpose of consistency.
The network-observability-release-notes.adoc file will dwindle with each PR while the network-observability-operator-release-notes-archive.adoc file will grow.
In as many cases as possible, such as:
[id="network-observability-channel-removal-1.4_{context}"]
== Channel removal
existing ID in network-observability-release-notes.adoc has been used in the new module.
Since not all content applies to every OCP branch, it is possible there will be cherry-pick failures. This will likely apply to release notes since it has been 1 assembly file and not all content is applicable to all OCP branches.
I will manually verify content on each breach, and create manual cherry-picks accordingly.
OSDOCS-15827 [NETOBSERV] Refactor release notes 1.6.0 #102310 must be merged first. Then rebase to pick up 1.6.0