1,623
edits
PostCrash: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
{{DRAFT}} | {{DRAFT}} | ||
The | The two primary goals of this project is to | ||
The project will require changes to | * Ensure that more users find relevant info about their crashes as well as info about how to avoid crashes in general. | ||
* Engage with users who provided an e-mail address in the Crash Reporter by letting them know whenever a known crash is fixed. | |||
A secondary goal is to | |||
* Develop about:crashes into a more useful resource for advanced users, with more info about the crashes upfront (e.g. signature, bug status, Firefox fix status, etc). | |||
The project will require changes to Session Restore, SUMO, Socorro, and possibly about:crashes in order to supply the required functionality. | |||
= Session Restore dialog = | |||
[[File:Post-crash_session_restore_flowchart.png|200px|thumb|right]] | |||
We want to make sure that more users are exposed to the already existing troubleshooting info about specific crashes, as well as general tips and advice on how to minimize crashes by keeping plugins up to date, etc. | |||
A good opportunity to do that is just after Firefox resumes from a crash. The Session Restore dialog should check if Firefox has crashed more than x (e.g. 3) times in the last 24 hours. If so, it should at the very least display general tips/advice for avoiding crashes, but it should also query Socorro/SUMO to see if there is specific support available for the crash and show that as well. | |||
The flowchart to the right illustrates the desired logic. | |||
On the SUMO side, there would be specific articles for known crash signatures (this is already the case for many crashes today), as well as a generic checklist guide for things a user should do to avoid crashes. | |||
== Changes to SUMO == | |||
* Add a webservice call that, given a signature and locale, searches for relevant content on SUMO and returns a URI. The web service should work as follows: | |||
*# If a canonical article exists for crash_signature (top search result), return the title and URL | |||
*# Else if other search results exist for crash_signature (e.g. forum threads), return URL to search results | |||
== Changes to Socorro == | |||
* Add a webservice call. Given crash id, return signature, associated plugin, associated bugzilla id and bug status. | |||
= about:crashes = | = about:crashes = | ||
| Line 30: | Line 52: | ||
Question: | Question: | ||
* Should we show both hangs and crashes? Users may load the page and see nothing but hangs. Does it make more sense to (perhaps by default) just show crashes? | * Should we show both hangs and crashes? Users may load the page and see nothing but hangs. Does it make more sense to (perhaps by default) just show crashes? | ||
= User email contact = | = User email contact = | ||
After discussion (see chofmann's comments below for background), we think the best way to solve this is with a manual process rather than an automated one | After discussion (see chofmann's comments below for background), we think the best way to solve this is with a manual process rather than an automated one, something like the following: | ||
* During the release process, a QA team member should collect a set of bugs fixed in the release and match with crash signatures. | * During the release process, a QA team member should collect a set of bugs fixed in the release and match with crash signatures. | ||