This is an old revision of the document!
Office Hours bugbusting topics.
These are MarkLinimon's ideas for specific topics to work on to help focus efforts during any type of bugbusting session.
the information in this page was adapted from the notes from the bugbusting working session in Kitchener, Ontario, Canada in May 2019.
Conventions
- PR refers to a Bugzilla Problem Report.
- DR refers to a Phabricator Differential Revision.
Let's just term them “issues” from here on.
Note that PRs contain a mix of suggested patches along with what is truly a Problem Report; the DRs are almost all patches.
Working On Existing Issues With Patches
Resources
- Bugzilla
- all base system PRs with patches, but assigned to no one (259)
- Phabricator
- base system DRs (> 1000)
- all DRs (1000s)
- needs review (120?)
- I do not know how to get a summary report to get the exact totals.
- How to search for “DRs with no reviewer?” Does not seem possible.
How To Find Things To Work On
- Bugzilla
- PRs with patches (see above)
- PRs assigned to particular mailing lists, e.g. net@
- except in a few cases, not granular enough
- tip: run general report and sort by assignee
- one or more keywords
- our list of keywords is sparse; the taxonomy needs to be defined better.
- see XXX for slightly longer explanations.
- Phabricator
- can create custom queries, but somewhat cumbersome
- I can't figure out how to query “assigned to no one”
- Should there be a policy to say “all DRs must a non-null reviewer”? even if it is a group?