|Release target||Firefox 6|
|Product manager||Asa Dotzler|
|Directly Responsible Individual||Nicholas Nethercote|
|Lead engineer||Nicholas Nethercote|
|QA lead||Vlad Ghetiu (irc: vladg)|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
Greatly improve about:memory.
2. Users & use cases
about:memory should be the first place anyone looks for any problem or question related to memory usage. (In particular, it should subsume OS tools like 'top', 'ps' and the Windows Task Manager.) If it doesn't answer the question, then more advanced tools can be used.
In particular, it will be very useful in bug reports. People often currently say vague things like "Firefox was using 1GB of memory" without explaining how they got that number. By cutting + pasting about:memory things will be a lot clearer.
- Cutting + pasting the contents of about:memory into a text box should produce highly readable output.
- Eventually, most interesting parts of memory (eg. the used part of the heap) should be marked as being owned by a particular part of the system.
- Per-tab (or something like that) information.
- Stage 1: bug 633653.
After that, much of it can be done gradually, in a bug-by-bug fashion.
Stage 2: Design
5. Functional specification
6. User experience design
- See screenshots in bug 633653 for stage 1.
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
|Engineering team||Desktop front-end|
Team status notes
|Quality assurance||Ready to land in Firefox 6||`|