-
Notifications
You must be signed in to change notification settings - Fork 2k
jira-lifecycle-plugin: update target version for 4.11 #31412
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
jira-lifecycle-plugin: update target version for 4.11 #31412
Conversation
This PR updates the `target_version` for the `release-4.11` and `openshift-4.11` branches to `4.11.z`.
|
@AlexNPavel: 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. |
|
Fixes DPTP-3071. |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AlexNPavel, bear-redhat, sdodson 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 |
|
@AlexNPavel: 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 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)
….z bugs (#31442) 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 (#31412), 2022-08-17). [1]: openshift/cluster-version-operator#824 (comment)
This PR updates the
target_versionfor therelease-4.11andopenshift-4.11branches to4.11.z./cc @bradmwilliams