-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[4.11 GA] Update bugzilla configuration #31215
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
Conversation
Signed-off-by: Jakub Guzik <[email protected]>
|
/hold |
|
@jmguzik: 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bear-redhat, jmguzik 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 |
|
/unhold |
|
@jmguzik: 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. |
Returning to the defaults. This happened for the Bugzilla plugin in 3029e8b ([4.11 GA] Update bugzilla configuration (openshift#31215), 2022-08-10), but the Jira plugin was overlooked then. The main benefit of the defaults is that MODIFIED and ON_QA 4.12.0 bugs may fail to address the issue, and we don't want to be backporting changed into 4.11.z until we know the 4.12 analog actually fixed the issue.
…11 (#32254) Returning to the defaults. This happened for the Bugzilla plugin in 3029e8b ([4.11 GA] Update bugzilla configuration (#31215), 2022-08-10), but the Jira plugin was overlooked then. The main benefit of the defaults is that MODIFIED and ON_QA 4.12.0 bugs may fail to address the issue, and we don't want to be backporting changed into 4.11.z until we know the 4.12 analog actually fixed the issue.
Previous PR for reference: #26898
/cc @bear-redhat
Signed-off-by: Jakub Guzik [email protected]