Skip to content

Meta: random bug triage assignments #4849

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
msullivan opened this issue Apr 4, 2018 · 5 comments
Closed

Meta: random bug triage assignments #4849

msullivan opened this issue Apr 4, 2018 · 5 comments

Comments

@msullivan
Copy link
Collaborator

We have a ton of bug backlog that is just sitting around without ever getting a fresh look.

One strategy might be to randomly assign everyone on the core team 5 or 10 bugs a week to take a look at, and:

  • Make sure it is triaged reasonably
  • Check to see whether it is still a bug
  • Comment about what would be needed for a fix, if they know
  • If a fix is easy or they have spare cycles, maybe fix it!

The rust team did something similar when I was an intern there, and I was a fan

@emmatyping
Copy link
Member

I think this could be useful. Several months ago I went through about 30 issues and tested them. I think I found one or two issues that were no longer problems.

My only concern is that all of the core team is already highly pressed for time.

@ilevkivskyi
Copy link
Member

ilevkivskyi commented Apr 4, 2018

I did this myself few times (I mean going through really old bugs and checking if they are still not fixed). This indeed helped to close quite a few issues (and duplicates). But last months I didn't have time for this. By the way this may be a good task for mypy sprints at PyCon. Last year the topic was usability issues, we can of course continue this year, or choose another topic -- closing old issues :-)

@ilevkivskyi
Copy link
Member

@msullivan Another (somewhat related) idea is about tests currently skipped in mypy. I remember some time ago that few tests with -skip now actually work. I think it makes sense to check them and enable those that work now.

@JukkaL
Copy link
Collaborator

JukkaL commented Apr 5, 2018

This could be useful. There are probably some open bugs that would be quick to fix for somebody with the right context. Implementing this wouldn't too hard either: a cron job that does a GitHub API call and sends a few emails might almost be sufficient. We'd probably also want to avoid sending repeated emails about the same issues. For example, we could email about a particular issue at most once every 6 months.

Some analysis: If we'd send 5 bugs to 5 people every week, we'd cover about 1300 issues a year (probably less since people won't always be available).

@ilevkivskyi Going through skipped tests is a good idea. It's probably fine to do this only once in a while.

@hauntsaninja
Copy link
Collaborator

This never happened; if there's time and appetite for something like this, we can open a new issue

@hauntsaninja hauntsaninja closed this as not planned Won't fix, can't repro, duplicate, stale Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants