Confirmed users
360
edits
DOM/Engineering: Difference between revisions
Jump to navigation
Jump to search
→Bugs: triage process, tiny crash reporting changes
(→Building Firefox: add some more build and config info that's somewhat redundant but helps with completionism) |
(→Bugs: triage process, tiny crash reporting changes) |
||
| Line 59: | Line 59: | ||
*** You can opt to receive bugmail for all activity in a given component without being CC'ed on the bug via the preferences' [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch Component Watching] preferences page. While this is useful, it can be a bit much. Messages you receive because you're watching a component will have an "X-Bugzilla-Reason" header value of "None" that you can use to filter on to differentiate from reasons like "CC". "X-Bugzilla-Watch-Reason" will also include "Component-Watcher" in that case among its other space-delimited terms. | *** You can opt to receive bugmail for all activity in a given component without being CC'ed on the bug via the preferences' [https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch Component Watching] preferences page. While this is useful, it can be a bit much. Messages you receive because you're watching a component will have an "X-Bugzilla-Reason" header value of "None" that you can use to filter on to differentiate from reasons like "CC". "X-Bugzilla-Watch-Reason" will also include "Component-Watcher" in that case among its other space-delimited terms. | ||
*** You can also watch what your team-mates are doing by using the "User Watching" functionality on the [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences] preferences page. "X-Bugzilla-Reason" will be "None" in this case just like for component watching, but you can filter using "X-Bugzilla-Who" which will be the email address of the watched person, as well as "X-Bugzilla-Watch-Reason" which will also include their email address and terms that identify their relation to the bug such as "AssignedTo" and "CC" separated by spaces. | *** You can also watch what your team-mates are doing by using the "User Watching" functionality on the [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences] preferences page. "X-Bugzilla-Reason" will be "None" in this case just like for component watching, but you can filter using "X-Bugzilla-Who" which will be the email address of the watched person, as well as "X-Bugzilla-Watch-Reason" which will also include their email address and terms that identify their relation to the bug such as "AssignedTo" and "CC" separated by spaces. | ||
** Triage: However, that all can get a bit overwhelming. You don't need to read every bug that comes into your mailbox. Which is why we have a triage process for components. Triagers will go through un-triaged bugs in a component and evaluate them and set a [[BMO/How_to_Use_Bugzilla#needinfo_flag|needinfo flag]] or assignee to take next steps to deal with the bug. | ** Triage: However, that all can get a bit overwhelming. You don't need to read every bug that comes into your mailbox. Which is why we have a triage process for components. Triagers will go through un-triaged bugs in a component and evaluate them and set a [[BMO/How_to_Use_Bugzilla#needinfo_flag|needinfo flag]] or assignee to take next steps to deal with the bug. [https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md The triage process is documented in the mozilla/bug-handling github repo]. | ||
=== Security Bugs === | === Security Bugs === | ||
| Line 66: | Line 66: | ||
* null pointer crashes should be fixed but don't need the whole process. | * null pointer crashes should be fixed but don't need the whole process. | ||
=== | === Crash reports === | ||
Firefox binaries are instrumented with crash-reporting handlers. These crash reports are sent to https://crash-stats.mozilla.com/ where they are processed and surfaced. Users can see a list of crashes they have personally reported by going to about:crashes in their browser. | |||
There's a variety of information on how to understand a crash report: | There's a variety of information on how to understand a crash report: | ||
* [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting/Understanding_crash_reports MDN's Understanding Crash Reports Page] | * [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting/Understanding_crash_reports MDN's Understanding Crash Reports Page] | ||