CrashKill/2012-09-04: Difference between revisions

no edit summary
(Created page with "Welcome to the first Stability Newsletter! For some time now, the crashkill team has been thinking about publishing a regular newsletter to the broader Mozilla community. The goa...")
 
No edit summary
Line 1: Line 1:
Welcome to the first Stability Newsletter! For some time now, the crashkill team has been thinking about publishing a regular newsletter to the broader Mozilla community. The goal is to engage users and developers in helping us improve the stability of all our products. The newsletter will cover a wide range of topics and information about crashes and crash analysis. We might focus on special topics, crash trends or simply provide a list of bugs we want help reproducing. The newsletter will be published twice during a full release cycle, one week after we merge from m-c to aurora and two weeks prior to release.  
Welcome to the first Stability Newsletter! For some time now, the crashkill team has been thinking about publishing a regular newsletter to the broader Mozilla community. The goal is to engage users and developers in helping us improve the stability of all our products. The newsletter will cover a wide range of topics relating to crashes and crash analysis. We might focus on particular problems, crash trends or simply provide a list of bugs we want help reproducing. The newsletter will be published twice during a full release cycle, one week after we merge from m-c to Aurora and two weeks prior to Release.  


==Stability 101==
==Stability 101==


Since this is our first newsletter, we thought it would be good to cover a few basics.
Since this is our first newsletter, we thought it would be good to cover a few basics for those who may not be as familiar with crashkill.


* Meetings
* Meetings
** The crashkill team meets on Monday morning at 10:00am PT in Zombocom (in person and on vidyo).  
** The crashkill team meets on Monday morning at 10:00am PT in Zombocom (in person and on vidyo).  
** Organized crash triage is on an ad-hoc and as needed basis.
** Members of the crashkill team attend and provide a stability report during the twice weekly Channel Meeting as well as the weekly Firefox Platform Meeting.
* Queries/Tools
* Queries/Tools
** We use [[https://crash-stats.mozilla.com/products/Firefox Socorro]] as our primary tool to run reports, search and track stability issues.
** We use [[https://crash-stats.mozilla.com/products/Firefox Socorro]] as our primary tool to run reports, search and track stability issues.
** We often have the need to generate a number of manual reports to help analyze and diagnose a particular issue. Kairo has many in his own directory.
** We often have the need to generate a number of manual reports to help analyze and diagnose a particular issue. Kairo has many in his own [[https://crash-analysis.mozilla.com/rkaiser/ directory]].
** Manual reports are often temporary until we can integrate them into Socorro. Other times we need a manual report to track a short-term issue.
* Wikis
* Wikis
** The [https://wiki.mozilla.org/CrashKill crashkill]] wiki is a pointer to meeting notes, queries, reports and other analysis tools.
* IRC
* IRC
** We hang out in #crashkill on irc
** We hang out in #crashkill on irc
Confirmed users
2,492

edits