would like to have a label `blocked` for marking issues blocked. about core

[sesheta]

@harshad16: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it will accept the issue by applying the
triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[goern]

sounds good to me. what do we do with blocked issues and pull requests? or is that just an informational label?

[harshad16]

It is an informational label to communicate with contributor that work is in progress though blocked with some reason.

what do we do with blocked issues and pull requests?

• we would try to unblock them based on priority or address them more in sig meetings.

[VannTen]

Should that be a standalone labels, or part of lifecycle/* ? (lifecycle/active )
Or another one ?

[harshad16]

Great question.
Any place would work.

As lifecycle labels are from Kubernetes, we can check if the blocked label is already present.

[goern]

Kubernetes does not have these semantics, they have issue that blocks releases, but they don't indicate that an issue is blocked... https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.yaml

putting it in the lifecycle context makes sense...

[VannTen]

Applying lifecycle labels is done by prow though ? We should check if we can add our own stuff somewhere in prow config.

[goern]

adding at to https://github.com/operate-first/apps/blob/master/prow/overlays/smaug/plugins.yaml#L6 should at least enable us to do /label lifecycle/blocked, I'm unsure about /lifecycle blocked

[codificat]

reviewing this today, we agreed that the status available via the project board is enough for the time being
/close

[sesheta]

@codificat: Closing this issue.

In response to this:

reviewing this today, we agreed that the status available via the project board is enough for the time being
/close

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.