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.

Sign up for GitHub

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

Jump to bottom

OBSDOCS-748: release notes for Cluster Observability Operator 0.1.1 #70674

Merged
merged 1 commit into from
Jan 29, 2024
Merged

OBSDOCS-748: release notes for Cluster Observability Operator 0.1.1 #70674

merged 1 commit into from
Jan 29, 2024

Conversation

bburt-rh
Copy link
Contributor

@bburt-rh bburt-rh commented Jan 23, 2024 •
edited

This PR is for the Cluster Observability Operator 0.1.1 release that is scheduled for January 25, 2024. Do not merge until this date.

Version(s): 4.11+

Issue: https://issues.redhat.com/browse/OBSDOCS-748

Link to docs preview: https://70674--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/cluster_observability_operator/cluster-observability-operator-release-notes

QE review:

  • QE has approved this change.

Additional information:
This PR updates the COO release notes with information describing the changes in the 0.1.1 release.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 23, 2024 •
edited by openshift-ci bot

@bburt-rh: This pull request references OBSDOCS-748 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:

Version(s): 4.11+

Issue: https://issues.redhat.com/browse/OBSDOCS-748

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 23, 2024
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 23, 2024
@openshift openshift deleted a comment from openshift-ci-robot Jan 23, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jan 23, 2024 •
edited

🤖 Tue Jan 23 15:43:23 - Prow CI generated the docs preview: https://70674--ocpdocs-pr.netlify.app

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 23, 2024 •
edited by openshift-ci bot

@bburt-rh: This pull request references OBSDOCS-748 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:

Version(s): 4.11+

Issue: https://issues.redhat.com/browse/OBSDOCS-748

Link to docs preview: https://70674--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/cluster_observability_operator/cluster-observability-operator-release-notes

QE review:

  • QE has approved this change.

Additional information:
This PR updates the COO release notes with information describing the changes in the 0.1.1 release.

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.

@danielmellado
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2024
@bburt-rh bburt-rh marked this pull request as draft January 23, 2024 15:23
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2024
@bburt-rh bburt-rh added this to the Continuous Release milestone Jan 23, 2024
@openshift openshift deleted a comment from openshift-ci-robot Jan 23, 2024
@bburt-rh bburt-rh marked this pull request as ready for review January 23, 2024 15:33
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2024
@jan--f
Copy link
Contributor

jan--f commented Jan 23, 2024

This
/lgtm

We don't need to mention in the release notes that this stays a tech preview release right?

@bburt-rh
Copy link
Contributor Author

We don't need to mention in the release notes that this stays a tech preview release right?

@jan--f If you look at the rendered preview link in the description, you'll see that the Tech Preview admonition remains at the top of the topic. I'll only remove it when the COO goes GA.

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jan 23, 2024

@bburt-rh: 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.

@lihongyan1
Copy link

/lgtm

@stevsmit stevsmit added peer-review-in-progress Signifies that the peer review team is reviewing this PR do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Jan 24, 2024
@stevsmit
Copy link
Member

LGTM

@stevsmit stevsmit added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jan 24, 2024
@bburt-rh bburt-rh removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 24, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 24, 2024 •
edited by openshift-ci bot

@bburt-rh: This pull request references OBSDOCS-748 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:

This PR is for the Cluster Observability Operator 0.1.1 release that is scheduled for January 25, 2024. Do not merge until this date.

Version(s): 4.11+

Issue: https://issues.redhat.com/browse/OBSDOCS-748

Link to docs preview: https://70674--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/cluster_observability_operator/cluster-observability-operator-release-notes

QE review:

  • QE has approved this change.

Additional information:
This PR updates the COO release notes with information describing the changes in the 0.1.1 release.

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.

@bburt-rh bburt-rh merged commit 8d424aa into openshift:main Jan 29, 2024
2 checks passed
@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.11

@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.12

@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.13

@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.14

@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.15

@openshift-cherrypick-robot
Copy link

@bburt-rh: #70674 failed to apply on top of branch "enterprise-4.11":

Patch is empty.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To record the empty patch as an empty commit, run "git am --allow-empty".
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.11

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
Copy link

@bburt-rh: #70674 failed to apply on top of branch "enterprise-4.12":

Applying: OBSDOCS-748-release-notes-for-coo-0.1.1
Using index info to reconstruct a base tree...
M	monitoring/cluster_observability_operator/cluster-observability-operator-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging monitoring/cluster_observability_operator/cluster-observability-operator-release-notes.adoc
CONFLICT (content): Merge conflict in monitoring/cluster_observability_operator/cluster-observability-operator-release-notes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-748-release-notes-for-coo-0.1.1
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

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

@openshift-cherrypick-robot
Copy link

@bburt-rh: #70674 failed to apply on top of branch "enterprise-4.13":

Applying: OBSDOCS-748-release-notes-for-coo-0.1.1
Using index info to reconstruct a base tree...
M	monitoring/cluster_observability_operator/cluster-observability-operator-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging monitoring/cluster_observability_operator/cluster-observability-operator-release-notes.adoc
CONFLICT (content): Merge conflict in monitoring/cluster_observability_operator/cluster-observability-operator-release-notes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-748-release-notes-for-coo-0.1.1
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

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.

@openshift-cherrypick-robot
Copy link

@bburt-rh: new pull request created: #70924

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 openshift-cherrypick-robot mentioned this pull request Jan 29, 2024
Merged
@openshift-cherrypick-robot
Copy link

@bburt-rh: new pull request created: #70925

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 openshift-cherrypick-robot mentioned this pull request Jan 29, 2024
Merged
@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.11

@openshift-cherrypick-robot
Copy link

@bburt-rh: new pull request created: #70939

In response to this:

/cherrypick enterprise-4.11

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 openshift-cherrypick-robot mentioned this pull request Jan 29, 2024
Merged
@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.12

@openshift-cherrypick-robot
Copy link

@bburt-rh: new pull request created: #70941

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

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 29, 2024
Merged
@bburt-rh
Copy link
Contributor Author

/cherrypick enterprise-4.13

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 29, 2024
Merged
@openshift-cherrypick-robot
Copy link

@bburt-rh: new pull request created: #70942

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
Reviewers

@stevsmit stevsmit stevsmit left review comments

@jan--f jan--f Awaiting requested review from jan--f

@danielmellado danielmellado Awaiting requested review from danielmellado

@lihongyan1 lihongyan1 Awaiting requested review from lihongyan1

Assignees

@jan--f jan--f

@danielmellado danielmellado

@lihongyan1 lihongyan1

Labels
branch/enterprise-4.11 branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 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 qe-approved Signifies that QE has signed off on this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
Continuous Release
Development

Successfully merging this pull request may close these issues.

None yet
8 participants
@bburt-rh @openshift-ci-robot @ocpdocs-previewbot @danielmellado @jan--f @lihongyan1 @stevsmit @openshift-cherrypick-robot