Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OBSDOCS-972: Logging- Remove confusing support statement for splunk fields deprecation #74643

Merged
merged 1 commit into from
Apr 16, 2024

Conversation

shreyasiddhartha
Copy link
Contributor

@shreyasiddhartha shreyasiddhartha commented Apr 15, 2024

Change type: Doc update; Logging- Remove confusing support statement for splunk fields deprecation

Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-972

Fix Version: 4.13+

Doc Preview: https://74643--ocpdocs-pr.netlify.app/openshift-dedicated/latest/logging/logging_release_notes/logging-5-9-release-notes.html#logging-release-notes-5-9-0-deprecation-notice

SME Review: @jcantrill
QE Review: @kabirbhartiRH
Peer Review: @bhardesty

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 15, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 15, 2024

@shreyasiddhartha: This pull request references OBSDOCS-972 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Change type: Doc update; Logging- Remove confusing support statement for splunk fields deprecation

Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-972

Fix Version: 4.13+

Doc Preview:

SME Review:
QE Review:
Peer Review:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 15, 2024
Copy link

openshift-ci bot commented Apr 15, 2024

@shreyasiddhartha: 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/test-infra repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 15, 2024

@shreyasiddhartha: This pull request references OBSDOCS-972 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Change type: Doc update; Logging- Remove confusing support statement for splunk fields deprecation

Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-972

Fix Version: 4.13+

Doc Preview: https://74643--ocpdocs-pr.netlify.app/openshift-dedicated/latest/logging/logging_release_notes/logging-5-9-release-notes.html#logging-release-notes-5-9-0-deprecation-notice

SME Review:
QE Review:
Peer Review:

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

@jcantrill jcantrill left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 15, 2024

@shreyasiddhartha: This pull request references OBSDOCS-972 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Change type: Doc update; Logging- Remove confusing support statement for splunk fields deprecation

Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-972

Fix Version: 4.13+

Doc Preview: https://74643--ocpdocs-pr.netlify.app/openshift-dedicated/latest/logging/logging_release_notes/logging-5-9-release-notes.html#logging-release-notes-5-9-0-deprecation-notice

SME Review: @jcantrill
QE Review:
Peer Review:

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 openshift-eng/jira-lifecycle-plugin repository.

@kabirbhartiRH
Copy link

/lgtm

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 16, 2024

@shreyasiddhartha: This pull request references OBSDOCS-972 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Change type: Doc update; Logging- Remove confusing support statement for splunk fields deprecation

Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-972

Fix Version: 4.13+

Doc Preview: https://74643--ocpdocs-pr.netlify.app/openshift-dedicated/latest/logging/logging_release_notes/logging-5-9-release-notes.html#logging-release-notes-5-9-0-deprecation-notice

SME Review: @jcantrill
QE Review: @kabirbhartiRH
Peer Review:

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 openshift-eng/jira-lifecycle-plugin repository.

@shreyasiddhartha
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Apr 16, 2024
@bhardesty
Copy link
Contributor

/label peer-review-in-progress

@bhardesty
Copy link
Contributor

/remove-label peer-review-needed

@openshift-ci openshift-ci bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Apr 16, 2024
Copy link
Contributor

@bhardesty bhardesty left a comment

Choose a reason for hiding this comment

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

LGTM!

@bhardesty
Copy link
Contributor

/label peer-review-done

@openshift-ci openshift-ci bot added the peer-review-done Signifies that the peer review team has reviewed this PR label Apr 16, 2024
@bhardesty
Copy link
Contributor

/remove-label peer-review-in-progress

@openshift-ci openshift-ci bot removed the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Apr 16, 2024
@shreyasiddhartha
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 16, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 16, 2024

@shreyasiddhartha: This pull request references OBSDOCS-972 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Change type: Doc update; Logging- Remove confusing support statement for splunk fields deprecation

Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-972

Fix Version: 4.13+

Doc Preview: https://74643--ocpdocs-pr.netlify.app/openshift-dedicated/latest/logging/logging_release_notes/logging-5-9-release-notes.html#logging-release-notes-5-9-0-deprecation-notice

SME Review: @jcantrill
QE Review: @kabirbhartiRH
Peer Review: @bhardesty

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 openshift-eng/jira-lifecycle-plugin repository.

@ShaunaDiaz
Copy link
Contributor

@shreyasiddhartha I don't see a Change Management email on this one, but it seems like it's a category that needs one, even if the "inform" special type. Please check with your DPM and the OpenShift docs manual.

@ShaunaDiaz
Copy link
Contributor

/remove-label merge-review-needed

@ShaunaDiaz
Copy link
Contributor

/cherrypick enterprise-4.16

@openshift-ci openshift-ci bot removed the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 16, 2024
@ShaunaDiaz
Copy link
Contributor

/cherrypick enterprise-4.15

@ShaunaDiaz
Copy link
Contributor

/cherrypick enterprise-4.14

@ShaunaDiaz
Copy link
Contributor

/cherrypick enterprise-4.13

@openshift-cherrypick-robot

@ShaunaDiaz: new pull request created: #74730

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/test-infra repository.

@openshift-cherrypick-robot

@ShaunaDiaz: new pull request created: #74731

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/test-infra repository.

@openshift-cherrypick-robot

@ShaunaDiaz: new pull request created: #74732

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/test-infra repository.

@openshift-cherrypick-robot

@ShaunaDiaz: new pull request created: #74733

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants