Add explanation of how component-readiness gates .0 releases #1582
Conversation
dev-guide/component-readiness.md
Outdated
| fix the regression or | ||
| get BU to acknowledge and accept the regression. | ||
|
|
||
| The [Component Readiness dashboard](https://sippy.dptools.openshift.org/sippy-ng/component_readiness/main ) allows our organization to |
There was a problem hiding this comment.
nit: trailing whitespace on the URI:
| The [Component Readiness dashboard](https://sippy.dptools.openshift.org/sippy-ng/component_readiness/main ) allows our organization to | |
| The [Component Readiness dashboard](https://sippy.dptools.openshift.org/sippy-ng/component_readiness/main) allows our organization to |
| The [Component Readiness dashboard](https://sippy.dptools.openshift.org/sippy-ng/component_readiness/main ) allows our organization to | |
| The [Component Readiness dashboard](https://sippy.dptools.openshift.org/sippy-ng/component_readiness/main ) allows our organization to |
Explains information available, how we will use that information, and who can approve exceptions.
deads2k
force-pushed
the
component-readiness-required
branch
from
c699dbb to
b11e5b3
Compare
|
@deads2k: all tests passed! Full PR test history. Your PR dashboard. 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. |
|
/lgtm |
deads2k
added
the
approved
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: 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 |
Explains information available, how we will use that information, and who can approve exceptions.