📖 Document the triage process

[fabriziopandini]

What this PR does / why we need it:
Writing down some practices / lesson learned from bug triage /backlog grooming sessions

/area documentation

/hold
For discussion in the office hours + give time to folks to review

[elmiko]

this is great, thanks @fabriziopandini , i just had a basic question and a couple nits.

[neolit123]

found some typos.

the process SGTM. i think there are 3 important labels that should always be on tickets.

• kind
• priority
• area

milestone can also be used for planning and triage.
but i see CAPI doesn't use milestones (any more)

is needs-triage going away too?

one problem with this triage process without milestone or needs-triage would be filtering of tickets that needs triage, it would need a negating query based on priority e.g.

is:issue is:open -label:priority/critical-urgent -label:priority/important-soon -label:priority/important-longterm -label:priority/backlog -label:priorty/awaiting-more-evidence 

for kubeadm, since we use milestone it could be just:

is:open is:issue no:milestone

[fabriziopandini]

Found a couple of interesting discussions about how things are managed in K8s and why; I'm looking into this:

• https://groups.google.com/a/kubernetes.io/g/dev/c/QFWGOkHQegA/m/Bbdoc_2UAgAJ
• we should not auto-close help-wanted and good-first-issue issues kubernetes/test-infra#27951
• Don't auto-close triaged issues, require re-triage after 1yr kubernetes/test-infra#28266

[elmiko]

content looks great here, my comments are all minor grammar nits.

[sbueringer]

Let me know when it's ready for review (just saying in case you forgot to remove "do not review")

[fabriziopandini]

@sbueringer PTAL at your convenience

[chrischdi]

Just a nit, otherwise lgtm

[sbueringer]

Overall makes sense to me! just a few nits

[sbueringer]

Thx!

/lgtm
/approve

/hold
(whenever you want to merge)

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: dac01833195387d354eb48d112efc38e8d373fa1

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fabriziopandini]

/hold cancel
we discussed this in the office hours in the last two meetings, no objections raised
All comments on the PR are addressed, let's move on