Additions:
- need to add system requirements on here, min and target
- web site/programming dependencies also? could be rolled into a "first run experience" requirement
- l10n specific bugs/features
This document should have a related documents section for links out to QA test plan, other high level plans, possibly marketing plan, etc.
We should also have supporting documents either easily visible from this document or as usual attached to the bug or tracking bug, for example design documents or usability reports, etc.
Organization:
As I said to cbeard in email, I still don't really grok what this "Feature Owner" structure is. In many cases it seems redundant with existing organizational processes. If this is to become a modus operandi for future development within Firefox, I think this needs to be discussed by the community first, rather than presented in this fashion. It's a pretty significant change and confusing it with discussion over the rest of the content of this document is not a good idea IMO. I'm removing myself as a co-author of this document until this is resolved. Ben 09:24, 8 Mar 2006 (PST)
P1 locales?
Talking about l10n features, should we try to add a list of locales to the PRD? I'm not sure in which status, if blocking or to-be-tracked or a different one.
Platform support
It's rather strange that RedHat Linux is reported as P1 and "All other Linux variants" are P2. What does that mean exactly?