Further prioritize bugs by keyword tagging (sec/crash/mlk/perf) and tracking flag
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Further prioritize bugs within groups by keyword tagging (sec/crash/mlk/perf/intermittend-failure) and tracking flag. This will increase the likelihood of a follow up. E.g. I want to know about topcrash fixes that have landed in Nightly and not in 47 before other non-sec, non-crash, non-regression bugs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the bug prioritization and Bugzilla metadata handling in bugbot. Define how sec, crash, mlk, perf, intermittent-failure, and the tracking flag affect ordering, including the Nightly-versus-47 example. Done means prioritized results consistently surface the requested categories and tracked fixes first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100