core-services/jira-lifecycle-plugin: Allow 4.11.z dependents for 4.10.z bugs#31442
Conversation
….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)
|
/approve |
|
/lgtm |
|
The bots appear to be on siesta at the moment! 😴 |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@wking: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@wking: Updated the
DetailsIn response to this:
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. |
….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.
Avoid:
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).