Fennec/Features/visualrefresh

From MozillaWiki
< Fennec‎ | Features
Revision as of 15:39, 21 April 2011 by Madhava (talk | contribs) (Created page with "{| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; backgro...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Feature Status ETA Owner
Visual Refresh (Gingerbread, Honeycomb) Concept YYYY-MM-DD Owner Name

Summary

Succinct summary of what this feature is all about.

Team

Who's working on this?

  • Feature Manager: tbd
  • Lead Developer:
  • Product Manager:
  • QA:
  • UX: Ian Barlow
  • Security:


Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

Next Steps

  • Assemble a "widget sheet" for froyo/gingerbread/honeycomb -- visuals only is fine

Open Issues

Unanswered questions, things that need to be explored, decisions that still need to be made, etc. Again, including the name of who's responsible for each item can be useful.

Related Bugs & Dependencies

Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Use Cases

Everyone loves use cases, so you should provide them if you can (and where it makes sense). The Channel Switcher Feature Page has some good examples.

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

  • Competitive landscape
  • Research & references
  • Whatever else is useful to the project.

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.


Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.