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-1415: Release notes for the Distributed Tracing 3.3.1 patch #83636

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

max-cx
Copy link
Contributor

@max-cx max-cx commented Oct 16, 2024

⚠️ This PR is tied to a patch release date, which is currently set to October 23 (Wednesday).

  • If the merge review gets delayed, you're welcome to ping mleonov on Slack.
  • If you have any questions, ping mleonov on Slack.

Version(s):

4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18

Issue:

https://issues.redhat.com/browse/OBSDOCS-1415

Link to docs preview:

https://83636--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr-tracing-rn.html#distr-tracing_3-3-1_distr-tracing-rn

https://83636--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-rn.html#otel_3-3-1_otel-rn

QE review:

  • QE has approved this change.

Additional information:

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

openshift-ci-robot commented Oct 16, 2024

@max-cx: This pull request references OBSDOCS-1415 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.18.0" version, but no target version was set.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 16, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 16, 2024

@max-cx: This pull request references OBSDOCS-1415 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.18.0" version, but no target version was set.

In response to this:

Version(s):

4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18

Issue:

https://issues.redhat.com/browse/OBSDOCS-1415

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@max-cx max-cx force-pushed the OBSDOCS-1415 branch 3 times, most recently from 59557a9 to 18bc8ea Compare October 17, 2024 13:33
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 17, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 17, 2024

@max-cx: This pull request references OBSDOCS-1415 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.18.0" version, but no target version was set.

In response to this:

Version(s):

4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18

Issue:

https://issues.redhat.com/browse/OBSDOCS-1415

Link to docs preview:

https://83636--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr-tracing-rn.html#distr-tracing_3-3-1_distr-tracing-rn

https://83636--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-rn.html#otel_3-3-1_otel-rn

QE review:

  • QE has approved this change.

Additional information:

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.

@max-cx max-cx force-pushed the OBSDOCS-1415 branch 12 times, most recently from af11a44 to cf521ca Compare October 18, 2024 08:21
@stevsmit stevsmit added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 21, 2024
@stevsmit
Copy link
Member

Content LGTM.

@stevsmit stevsmit merged commit 99f7f81 into openshift:main Oct 23, 2024
2 checks passed
@stevsmit
Copy link
Member

/cherry-pick enterprise-4.12

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.13

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.14

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.15

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.16

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.17

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84019

In response to this:

/cherry-pick 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.

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84020

In response to this:

/cherry-pick 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.

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84021

In response to this:

/cherry-pick 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.

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84022

In response to this:

/cherry-pick 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.

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.17

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.18

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.17

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.18

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84024

In response to this:

/cherry-pick 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.

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84025

In response to this:

/cherry-pick enterprise-4.18

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.

@stevsmit
Copy link
Member

/cherry-pick enterprise-4.16

@openshift-cherrypick-robot

@stevsmit: new pull request created: #84035

In response to this:

/cherry-pick 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants