Skip to content

Conversation

@ryanemerson
Copy link
Contributor

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 26, 2022

Hi @ryanemerson. Thanks for your PR.

I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jan 26, 2022
@openshift-ci openshift-ci bot requested review from awgreene and njhale January 26, 2022 18:55
Copy link
Member

@joelanford joelanford left a comment

Choose a reason for hiding this comment

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

Thanks for the PR! Just a few minor suggestions...

@codecov
Copy link

codecov bot commented Jan 26, 2022

Codecov Report

Merging #909 (4bfb402) into master (4e33928) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #909   +/-   ##
=======================================
  Coverage   52.18%   52.18%           
=======================================
  Files         103      103           
  Lines        9113     9113           
=======================================
  Hits         4756     4756           
  Misses       3451     3451           
  Partials      906      906           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e33928...4bfb402. Read the comment docs.

@joelanford
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 27, 2022
@joelanford
Copy link
Member

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelanford, ryanemerson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 27, 2022
@phantomjinx
Copy link

Is this likely to be merged soon please?

@phantomjinx
Copy link

Is this likely to be merged soon please?

Hey @joelanford, do you have a timeframe for when this is going into a release please?

@kevinrizza
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2022
@openshift-merge-robot openshift-merge-robot merged commit 9999f79 into operator-framework:master Feb 25, 2022
@kevinrizza
Copy link
Member

@phantomjinx usually we try to release minor versions of the registry on the same cadence as OLM releases, although our release process hasn't been the most consistent. our last release was only a few weeks ago, so my guess is it may be a little while until the next patch release. but if there's an urgent need for this patch, you could create an issue on this repository, tag this, and we can talk about cutting a release sooner in the upstream olm working group.

@ryanemerson
Copy link
Contributor Author

@kevinrizza I have created #925. I have included details of Operatorhub changes that explain why a release is needed by April, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants