Closed cahillsf closed 1 month ago
@nawazkh i see your name on this one from last release, would you like to assign this issue to yourself?
/area release
/triage accepted
can we dedup closing on of this or https://github.com/kubernetes-sigs/cluster-api/issues/9735 (probably this since the entire discussion is on the other issue)?
reopening as we do have some work for the docs that came out of this: https://github.com/kubernetes-sigs/cluster-api/issues/9735#issuecomment-1969592360
/kind documentation /priority important-soon
This issue is labeled with priority/important-soon
but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.
You can:
/triage accepted
(org members only)/priority important-longterm
or /priority backlog
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
Is this still something we want to work on?
i think it would be helpful, looks like it was added to improvement tasks for last cycle but no one picked it up.
for part 2, i did "overweigh" the CI team for release-1.8 and release-1.9 CI team also appears to be overweight compared to the other teams. can update the release docs to prefer this approach going forward
happy to grab this and open a PR, i think the only piece that is hazy is:
define what the CI team's "escalation path" should look like when they have reached the limits of their understanding/troubleshooting paths
this ambiguity is apparent in the CI team docs too https://github.com/kubernetes-sigs/cluster-api/tree/main/docs/release/role-handbooks/ci-signal#continuously-bug-triage:
We probably have to figure out some details about the overlap between the bug triage task here, release leads and Cluster API maintainers.
not sure if you have thoughts for a more "formal" approach here @sbueringer?
i can just make this reflective of what our current "process" here is. something along the lines of "post in #cluster-api slack channel to increase visibility. continue discussion in thread there. bring up in weekly meeting and/or spin off a dedicated zoom chat for a focused session if helpful..."
/assign cahillsf
I don't know if we want or need a more "formal" approach. Documenting the current state sounds reasonable
Related discussion: https://github.com/kubernetes-sigs/cluster-api/issues/9735
Carryover from: https://github.com/kubernetes-sigs/cluster-api/issues/9104