B2G/QA/Bugzilla/Advanced
Jump to navigation
Jump to search
Tips and Tricks:
- Quick Searching by typing in firefox URL
- Suggest creating a separate gmail account for bugzilla as you may end up getting tons and tons of emails about bugs.
- Other information about Bugzilla FAQ that doesn't necessarily impact doing work
Differences from other projects
- Whiteboard tags:
- [b2g-desktop-builds] : for desktop builds
- regression-window
- regression
- qa+ : qa needs to track
- qa- : qa does not need to track
- qa? : not sure if qa needs to track
- qa^ : qa believes that this bug needs to be raised in awareness
- [b2g-crash] : a crash that happens in b2g (note bugs could move to core if it is found to be a gecko crasher so it makes it easier to track crashing bugs this way.
- [feedback] : comes from user feedback
- Keyword tags:
- qawanted : bugs that need QA to help provide more information
- dogfood : added for people who submit through the dogfooding program.
- b2g-testdriver: added for people who submit through the testdrivers program
- unagi : when it happens on the unagi phone
- otoro : when it happens on the otoro phone
- polish : when it's a fixing/cleaning up the look and feel; it may not necessarily be blocking
- steps-wanted : need repro steps
- crash : a crashing bug
- hang : hanging bug
- dev-doc-needed: dev doc needed
- user-doc-needed: SUMO doc needed
- Other keywords
- Flags:
- Blocking-basecamp ?
- any bugs that you think block release.
- Blocking-basecamp ?
Base Camp blocking Priorities for Gaia
- P1 (assigned) - dogfood/smoketest blockers, required feature work for v1 ship, demo blockers, certification requirements, l10n impact, risky or high LOE work, work with long dependency changes
- P2 - Regressions, security bugs, severe crash/hang bugs, severe usability issues
- P3 - Less critical stability, stability, and performance bugs that still block v1, less severe usability issues