JavaScript:Bugzilla
This page explains how the JavaScript Team uses Bugzilla.
Bugzilla components
- Core::JavaScript Engine
- Core::JavaScript Engine: JIT
- Core::JavaScript: GC
- Core::JavaScript: Internationalization API
- Core::JavaScript: Standard Library
- Core::js-ctypes
Review flags
The JS team uses the review flags the same way as the rest of Gecko developer. The only different is the lack of "r-" when a review needs to be revisited, instead the review request is canceled with comments. The "r-" flag is used only in a few cases where multiple reviewers are requested on the same patch, and one of them is opposed to the changes.
Whiteboard flags
A few whiteboard flag are used today in the JS components:
- [#jsapi:crashes-retriage] Used for crash-stat crashes which might be harder to investigate alone. This whiteboard tag is used to cluster the analysis of crash-stat reports. (Owner: Ted Campbell)
- [qf] Used for any performance regression/improvement which can be part of the Quantum Flow effort of fixing known bugs. (Owner: Kannan Vijayan)
As a convention, anybody can follow the following naming for using the whiteboard to improve Bugzilla searches. However, note that whiteboard searches are not indexed in Bugzilla databases and this might lead to performance issues.
- [:nick:...] Used by the user :nick for managing bugs.
- [#channel:...] Used by members of the IRC #channel for managing bugs.
Priority Flags
Priority flags are set based on the current goals. The list of goals can be found in the JS Team document which list all the goals. The addon bugzilla triage helper can be used to set the P1, P2, P3 and P5 (no P4) flags
- P1: P1 goals or blockers, Security issues. (to be fix ASAP)
- P2: P2 goals or blockers. (scheduled to be fix in an upcoming version)
- P3: P3 goals or blockers. (backlog; to be fix one day)
- P5: (not a priority for Firefox product; might never be fixed)
Triage
The triage effort is currently held by the triage owners, and supported by Jason Orendorff and Nicolas B. Pierron. The list of non-prioritized bugs, is used to set the missing priority flags and whiteboard flags to the corresponding bugs.
A weekly meeting is held every Thursday to re-triage P1 which have no assigned person, no need-info or no activity for a while.