SVG:Bug searches
Jump to navigation
Jump to search
SVG bug searches
Important bugs
These are good searches to use if you're looking for something to work on, or looking for bugs that need to be prioritized. We should start using the priority field in Bugzilla to direct our work more, using the definitions for priorities as suggested by David.
- Bugs marked with 'crash'
- Bugs marked with 'hang'
- Bugs marked with 'perf' (SVG is too slow - add to hangs as well)
- Bugs marked with 'regression'
- Bugs marked as 'blocker', 'critical' or 'major' (not necessarily high priority if unlikely to be encountered by many people)
- Bugs marked with 'mlk' (memory leak bugs)
- Orange bugs
- Bugs marked with 'footprint' (SVG is using too much memory)
- Bugs marked with 'assertion'
- Bugs marked with 'mobile' (important for the mobile developmental work)
Tracked bugs
Bugs affecting branches
Requests for help
- Bugs marked with 'regressionwindow-wanted'
- Bugs marked with 'testcase-wanted'
- Bugs marked with 'stackwanted'
- Bugs marked with 'helpwanted'
- Bugs marked with 'dev-doc-needed'
- Bugs marked with 'technote' (needs technotes on devmo)
- Bugs marked with 'checkin-needed'
- Bugs that may need 'checkin-needed'
- Bugs that may need 'checkin-needed' (alternative query)
Other searches
- Bugs with [mentor=xxx]
- Bugs marked with 'access' (accessibility bugs - making things better for users with disabilities and special needs)
- Bugs marked with 'fonts' (font bugs)
- Bugs marked with 'rtl' (bugs with right-to-left writing system)
- Bugs marked with 'intl' (international issues)
- Bugs marked with 'pp' (platform parity bugs - bugs that don't exist on all platforms)
- Bugs marked with 'arch' (architecture cleanup)
- Bugs marked with 'autotest-issue' (bugs blocking development/deployment of automated tests)
- Bugs marked with 'APIchange'
Bug state
- testcase Indicates that the bug report contains a simplified test case.
- dev-doc-complete Indicates that developer documentation has been created for the bug report or its fix.