ProgramManagement/Firefox/2011-Q2-Goals: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
** Wiki pages for keep track of top crashes and issues for each channel. | ** Wiki pages for keep track of top crashes and issues for each channel. | ||
** Regular stability reports and summaries for channel meetings. | ** Regular stability reports and summaries for channel meetings. | ||
* {{ok|Evaluation and assessment of an algorithm for detecting explosive crashes. Once vetted, this will be integrated into Socorro. [https://bugzilla.mozilla.org/show_bug.cgi?id=629062 bug 629062] | * {{ok|Evaluation and assessment of an algorithm for detecting explosive crashes. Once vetted, this will be integrated into Socorro.}} [https://bugzilla.mozilla.org/show_bug.cgi?id=629062 bug 629062] | ||
** See how the algorithm performs during the FF5 release cycle and tweak appropriately. | ** See how the algorithm performs during the FF5 release cycle and tweak appropriately. | ||
* {{ok| | * {{ok|Initial discussions and thinking around how to handle content and jetpack crashes.}} | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=578687 bug 578687] | |||
* {{ok|Put in place a more concrete plan on how to make progress on some of the harder crashes ie: malware, plugins.}} | * {{ok|Put in place a more concrete plan on how to make progress on some of the harder crashes ie: malware, plugins.}} | ||
** We did a great job with browser crashes for FF4 but need to have a similar push for dealing with plugin issues and harder problems. | ** We did a great job with browser crashes for FF4 but need to have a similar push for dealing with plugin issues and harder problems. | ||
Revision as of 18:06, 29 April 2011
General Goals
- [ON TRACK] Ship Firefox 5 on the new Rapid Release schedule
Crashes & Stability
- [ON TRACK] Delivering a clear prioritized list of engineering requirements for the improving crash analysis to the Socorro team.
- Ensuring these are scheduled into Socorro releases and tracked.
- Regular sychs with the Socorro team.
- [ON TRACK] Framework and process for monitoring and communicating stability information that supports the new rapid release model.
- Wiki pages for keep track of top crashes and issues for each channel.
- Regular stability reports and summaries for channel meetings.
- [ON TRACK] Evaluation and assessment of an algorithm for detecting explosive crashes. Once vetted, this will be integrated into Socorro. bug 629062
- See how the algorithm performs during the FF5 release cycle and tweak appropriately.
- [ON TRACK] Initial discussions and thinking around how to handle content and jetpack crashes.
- bug 578687
- [ON TRACK] Put in place a more concrete plan on how to make progress on some of the harder crashes ie: malware, plugins.
- We did a great job with browser crashes for FF4 but need to have a similar push for dealing with plugin issues and harder problems.
- Try and give these initiatives more focus - regular discussions with outreach folks.