SIG-Scheduling: better issue management

[sanposhiho]

Describe the issue

/cc @kubernetes/sig-scheduling-leads

We should improve https://github.com/orgs/kubernetes/projects/165/views/1 to prioritize tasks better. Also, we should try triaging issues if we find them worthy to be worked on, at least.

[sanposhiho]

/sig scheduling

[sanposhiho]

What I'd like to see in the kanban board:

• Prioritization between triaged tasks
• Easy way to find the tasks that no one has taken a look (= awaiting the decision of whether triage it or not)
• Easy way to classify the PRs that are awaiting the first review and the ones that are awaiting the final reviews.

I'm not sure if all are feasible. Just spreading the ideas.

Anything else that might be good to have on Kanban board? @dom4ha @macsko

[sanposhiho]

Started to triage issues from the newer ones... But, there's a lot 😅

[sanposhiho]

Some thoughts:

• Prioritization between triaged tasks: Very first thing that we can do is using important-longterm etc labels, but I guess it's too rough? Other option is having a custom priority field with the number on the board, and sort the issues by it on Kanban. But, maybe that's a bit troublesome. We need to figure out what would fit us the most.
• Easy way to find the tasks that no one has taken a look (= awaiting the decision of whether triage it or not): We can list the issues that has need-triage label. But, among need-triage issues, there's some other kinds like need to discuss before triaging or not, need more information, etc. We can use triage/needs-information, I think. (Looks like we don't have triage/needs-discussion.
  • So, when the first contributor takes a look at an issue that no one has reacted yet, he/she has to add either triage/accepted or triage/needs-information.
• Easy way to classify the PRs that are awaiting the first review and the ones that are awaiting the final reviews." We can list the issues that don't have lgtm and approve issue vs the ones that have either of them.

TODO:

• [ ] make a documentation page about this issue management
• [ ] make a change in the dashboard
• [ ] close old (unimportant) issues

[helayoty]

@sanposhiho happy to help in this effort.

[sanposhiho]

@helayoty Yes, please! Do you have a permission to edit https://github.com/orgs/kubernetes/projects/165/views/1? The above my thought should be a good starting point for the enhancement.

[helayoty]

@sanposhiho , @dom4ha @macsko , I've modified couple of the dashboard views. Now the dashboard has:

• SIG overview view for all issues/PRs with sig/scheduling label categoried by repo and status.
• Release view which gets updated with any issue/PR gets added to the current milestone.
• PR reviews view which displays the reviewer/assignee for each PR.

In addition to other views to give maintainers grasp on more details:

• Enhancements Kanban
• Issues view for all issues across all repos
• PRs view for all PRs across all repos

When a new issue with sig/scheduling label is created, it will be added automatically to the project with Needs Triage status. And when a new PR with sig/scheduling label is opened, it will be added automatically also but with Needs Review status.

Now, we can go easily to the issues view and triage or add to release in the begining of each cycle. Then we can use the Release view to track the items during release cycle and PR review to assign PRs to sig maintainers.

cc @wojtek-t @johnbelamaric

[helayoty]

/assign @helayoty

[macsko]

I've modified couple of the dashboard views.

Thanks for doing that! Now it's much cleaner.

And when a new PR with sig/scheduling label is opened, it will be added automatically also but with Needs Review status.

Please note that this point is not valid for kubernetes/kubernetes PRs. Those are not put in the PR reviews and PRs views (and in any of these dashboard). Maybe it's worth improving that aspect (modify dashboard's workflows).

[sanposhiho]

Thanks a lot, @helayoty. It's shiningly better now.

this point is not valid for kubernetes/kubernetes PRs.

Yeah, looks like k/k PRs are not added as Needs Review. The filter implemented in the workflow is incorrect. I guess we can just remove label:bug anyway, right? since we'd like to manage all PRs/issues in the dashboard.

[helayoty]

@macsko @sanposhiho thanks for noticing that. Fixed now.

[helayoty]

Easy way to classify the PRs that are awaiting the first review and the ones that are awaiting the final reviews. @sanposhiho to address this request, I added new status Needs Final Approval to the PR view. Once all reviews is done, we can move the PR to this status.

[sanposhiho]

Perfect. I think we can close this issue now because, at least, the dashboard is refined. (feel free to reopen this if you have any more things to do) I know we have to iterate all the Need Triage ones, but I'd say that's another story. We should put effort evaluating each issue when have time..

/close

[k8s-ci-robot]

@sanposhiho: Closing this issue.

In response to this:

Perfect. I think we can close this issue now because, at least, the dashboard is refined. (feel free to reopen this if you have any more things to do) I know we have to iterate all the Need Triage ones, but I'd say that's another story. We should put effort evaluating each issue when have time..

/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-sigs/prow repository.

[dom4ha]

The views looks great! Thanks @helayoty @sanposhiho and @macsko

What I'd like to see in the kanban board:

• Prioritization between triaged tasks
• Easy way to find the tasks that no one has taken a look (= awaiting the decision of whether triage it or not)
• Easy way to classify the PRs that are awaiting the first review and the ones that are awaiting the final reviews.
• I'm not sure if all are feasible. Just spreading the ideas.

These all are important. Let's try to track enhancements since we're in that phase. Do you think we can come up with priorities or manage the order manually? (I see there's an option to override sorting)

[macsko]

Do you think we can come up with priorities or manage the order manually? (I see there's an option to override sorting)

I think we could just sort by hand in the Enhancements view (and slice or group by a milestone, to only focus on a specific release).

[helayoty]

important. Let's try to track enhancements since

The only way to filter priority label is creating a view similar to that: https://github.com/orgs/kubernetes/projects/165/views/10

[helayoty]

Do you think we can come up with priorities or manage the order manually? (I see there's an option to override sorting)

I think we could just sort by hand in the Enhancements view (and slice or group by a milestone, to only focus on a specific release).

Correct or you can filter the label field.