Support/RapidRelease/Firefox 6 tracking page

This is a page tracking support tasks for Firefox 5 shipping.

Roughly in order:

[ON TRACK] Track features that are making it into the release and make special note of any user facing/user affecting changes. Use the Features/Release Tracking page.
- - User-facing features on this train: F1
[ON TRACK] Try to anticipate early problems to be on the lookout for in later stages.
[ON TRACK] UX team check in.
- Michael is calling into weekly UX meetings.
- Possible features from them: Home tab

[NEW] Gauge user's initial response to a feature when it's introduced (via feedback). Highlight any red flags. If there's any confusion points, take note of them for documentation focus.
Devise a documentation strategy. Make a list of articles to change for each feature.
[ON TRACK] Attend triage meetings to know if a feature is going forward to beta or is staying on experimental. Note any bugs found that may be "shippable". Give feedback on the expected support experience.
Check in with QA to see if there are issues they've identified that we should keep an eye out for.
Right before ship: Brief community on potential beta issues.

Weekly feedback roundup (from input and support forums)
Summarize top SUMO and input issues for dev teams to help inform planning meetings
Write feature documentation (host KB sprint?)
Alert localizers (or do l10n on a schedule)
Localize feature documentation.
Update beta start page to highlight new features
Anticipate top issues that will likely crop up that we will ship with based on input and sumo
Track down owners of issues and get workarounds if possible. Or use SUMO threads to see what workarounds have been helping users.
Document top issues and link from front page

Contents