|Memory tooling backend|
|Product manager||Kevin Dangoor|
|Directly Responsible Individual||Kevin Dangoor|
|Lead engineer||Dave Camp|
|QA lead||Virgil Dicu|
|Product marketing lead||`|
|Additional members||Jan (Honza) Odvarko (firebug representative)|
Stage 1: Definition
1. Feature overview
Ultimately, we want to be able to provide tools that give Firefox users answers to the following questions:
is my page taking a lot of memory?
if it is, how do I fix it? (where is that memory going?)
am I allocating too many objects? if so, where?
For the first stage, we need to identify:
what information we can get from the system presently
what work needs to be done to get the information required to answer the questions above
The goal of this project now is to get the ball rolling so that the backend can provide the information we want so that a future release can provide the user-visible tooling.
2. Users & use cases
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
- See the status page.
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes