Features/Platform/Page Load and Crash Probes
Status
| Page Load and Crash Probes | |
| Stage | Draft |
| Status | ` |
| Release target | Firefox 11 |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Page Load and Crash Probes
|Feature stage=Draft |Feature status=` |Feature version=Firefox 11 |Feature health=OK |Feature status note=` }}
Team
| Product manager | ` |
| Directly Responsible Individual | Alex Keybl |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=`
|Feature feature manager=Alex Keybl |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
We'd like to start tracking overall crash and page load metrics in order to enable analysis such as average number of crashes per (n) page loads. The goal is to understand progress in our crash efforts and better focus future efforts.
Targeting landing on m-c for Firefox 11, with the opportunity to pull into Aurora/Beta if deemed low risk.
2. Users & use cases
Mozillians will benefit from metrics pulled from these probes, as we'll be able to better understand crash "pain".
All users should transparently report the number of page loads and crashes on a regular basis. Users will obviously benefit from the probing of of these two metrics as we'll be able to better prioritize crash efforts.
3. Dependencies
`
4. Requirements
- Client changes, inserting probes
- Ability to query/chart the data based upon product, version, channel, dates
- Keep in mind that we may want to correlate these numbers with crash reports in the future
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=We'd like to start tracking overall crash and page load metrics in order to enable analysis such as average number of crashes per (n) page loads. The goal is to understand progress in our crash efforts and better focus future efforts.
Targeting landing on m-c for Firefox 11, with the opportunity to pull into Aurora/Beta if deemed low risk. |Feature users and use cases=Mozillians will benefit from metrics pulled from these probes, as we'll be able to better understand crash "pain".
All users should transparently report the number of page loads and crashes on a regular basis. Users will obviously benefit from the probing of of these two metrics as we'll be able to better prioritize crash efforts. |Feature dependencies=` |Feature requirements=* Client changes, inserting probes
- Ability to query/chart the data based upon product, version, channel, dates
- Keep in mind that we may want to correlate these numbers with crash reports in the future
|Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-unnecessary | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-unnecessary |Feature security health=OK |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}