Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Aug 18, 2022

Avoid:

... expected dependent Jira Issue OCPBUGS-232 to target a version in 4.11.0, but it targets "4.11.z" instead...

Now that 4.11 is GA, 4.10.z backports can carry back both changes that landed pre-GA (4.11.0) and post-GA (4.11.z). Follows up on 8276887 (#31412).

….z bugs

Avoid [1]:

  ... expected dependent Jira Issue OCPBUGS-232 to target a version in 4.11.0, but it targets "4.11.z" instead...

Now that 4.11 is GA, 4.10.z backports can carry back both changes that
landed pre-GA (4.11.0) and post-GA (4.11.z).  Follows up on 8276887
(jira-lifecycle-plugin: update target version for 4.11 (openshift#31412),
2022-08-17).

[1]: openshift/cluster-version-operator#824 (comment)
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 18, 2022
@bradmwilliams
Copy link
Contributor

/approve

@sdodson
Copy link
Member

sdodson commented Aug 18, 2022

/lgtm

@bradmwilliams
Copy link
Contributor

The bots appear to be on siesta at the moment! 😴

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 18, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, hoxhaeris, sdodson, wking

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

The pull request process is described here

Details 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 Aug 18, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 18, 2022

@wking: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-merge-robot openshift-merge-robot merged commit b6e2c73 into openshift:master Aug 18, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 18, 2022

@wking: Updated the jira-lifecycle-plugin-config configmap in namespace ci at cluster app.ci using the following files:

  • key config.yaml using file core-services/jira-lifecycle-plugin/config.yaml
Details

In response to this:

Avoid:

... expected dependent Jira Issue OCPBUGS-232 to target a version in 4.11.0, but it targets "4.11.z" instead...

Now that 4.11 is GA, 4.10.z backports can carry back both changes that landed pre-GA (4.11.0) and post-GA (4.11.z). Follows up on 8276887 (#31412).

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.

@wking wking deleted the fix-4.10.z-Jira-backport-config branch August 18, 2022 15:28
wking added a commit to wking/openshift-release that referenced this pull request Aug 18, 2022
….z release-4.10 bugs

I'd reconfigured openshift-4.10 in 4b6110a
(core-services/jira-lifecycle-plugin: Allow 4.11.z dependents for
4.10.z bugs, 2022-08-17, openshift#31442), but forgot release-4.10.  Catch that
up in this commit.
openshift-merge-robot pushed a commit that referenced this pull request Aug 18, 2022
….z release-4.10 bugs (#31462)

I'd reconfigured openshift-4.10 in 4b6110a
(core-services/jira-lifecycle-plugin: Allow 4.11.z dependents for
4.10.z bugs, 2022-08-17, #31442), but forgot release-4.10.  Catch that
up in this commit.
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants