Silent Update whatsnew: Difference between revisions
No edit summary |
No edit summary |
||
| Line 52: | Line 52: | ||
|Feature engineering team=Release Engineering | |Feature engineering team=Release Engineering | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus | ||
|Feature qa notes=[https://wiki.mozilla.org/Features/Desktop/Silent_Update_whatsnew/TestPlan#Silent_Update_whatsnew Test Plan] | |||
}} | |||
Revision as of 13:51, 19 October 2011
Status
| Silent Update: Lessen the showing of the what's new page | |
| Stage | Landed |
| Status | Complete |
| Release target | Firefox 8 |
| Health | OK |
| Status note | Working with Product Marketing on the new channels to communicate to our users. |
{{#set:Feature name=Silent Update: Lessen the showing of the what's new page
|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 8 |Feature health=OK |Feature status note=Working with Product Marketing on the new channels to communicate to our users. }}
Team
| Product manager | Chris Lee |
| Directly Responsible Individual | Lawrence Mandel |
| Lead engineer | Laura Mesa |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Mihaela Velimiroviciu |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Chris Lee
|Feature feature manager=Lawrence Mandel |Feature lead engineer=Laura Mesa |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Mihaela Velimiroviciu |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
With Silent Update, the What's New page itself is less relevant to the user given we want to be "silent". However, there is a need for Product Marketing/Engagement to communicate to our users on a regular basis and the purpose of this feature page is to define those requirements.
2. Users & use cases
Ways to Minimize the What's New Page Experience Ideas:
- Decrease frequency - perhaps taper off
- Utilize new Home Tab
- Move link to bookmark
- Move link into some other area in the Menu bar
- A opt-in model
- Bigger "About Firefox" page to let users know What's New (LMesa)
- Start page (60-70% of users do not change the default)
- Home tab will replace Start page (options that allow people to customize)
- "Getting Started" bookmark
Notes:
- Also note that the snippet space as we know it will be replaced by the Home Tab as well
- Involve the UX people to help incorporate engagement touchpoints into UI changes coming
- First Run will not be touched
3. Dependencies
We already have the ability to enable or disable the what's new page on a per release basis. The client side work to provide this functionality is available with Firefox 4 and above. The remaining server side work is being done in bug 459972.
4. Requirements
Engagement/PMM Feature Requirements:
- Be able to tell people What's New within Firefox (updatable)
- Engagement touchpoints - email, Twitter, Facebook
- Promo spots for campaigns (ex. Webify Me) and products (mobile, apps, add-ons, etc)
- User alerts (ex. "Your Flash is out-of-date")
- (all of the above have the standard features of a web page - easily updatable; flexible in terms of A-B testing, rotating content, etc...vs something hard-coded into the browser chrome)
- Ability to push people off older versions (ex. warning people to upgrade from 3.6)
- A/B test who sees the what's new page (i.e. 95% see it, 5% don't see it) and track their engagement
Non-goals
`
Stage 2: Design
5. Functional specification
- The client side functionality was implemented for Firefox 4.
- The remaining server side work is being done in
bug 459972
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=With Silent Update, the What's New page itself is less relevant to the user given we want to be "silent". However, there is a need for Product Marketing/Engagement to communicate to our users on a regular basis and the purpose of this feature page is to define those requirements. |Feature users and use cases=Ways to Minimize the What's New Page Experience Ideas:
- Decrease frequency - perhaps taper off
- Utilize new Home Tab
- Move link to bookmark
- Move link into some other area in the Menu bar
- A opt-in model
- Bigger "About Firefox" page to let users know What's New (LMesa)
- Start page (60-70% of users do not change the default)
- Home tab will replace Start page (options that allow people to customize)
- "Getting Started" bookmark
Notes:
- Also note that the snippet space as we know it will be replaced by the Home Tab as well
- Involve the UX people to help incorporate engagement touchpoints into UI changes coming
- First Run will not be touched
|Feature dependencies=We already have the ability to enable or disable the what's new page on a per release basis. The client side work to provide this functionality is available with Firefox 4 and above. The remaining server side work is being done in bug 459972.
|Feature requirements=Engagement/PMM Feature Requirements:
- Be able to tell people What's New within Firefox (updatable)
- Engagement touchpoints - email, Twitter, Facebook
- Promo spots for campaigns (ex. Webify Me) and products (mobile, apps, add-ons, etc)
- User alerts (ex. "Your Flash is out-of-date")
- (all of the above have the standard features of a web page - easily updatable; flexible in terms of A-B testing, rotating content, etc...vs something hard-coded into the browser chrome)
- Ability to push people off older versions (ex. warning people to upgrade from 3.6)
- A/B test who sees the what's new page (i.e. 95% see it, 5% don't see it) and track their engagement
|Feature non-goals=` |Feature functional spec=*The client side functionality was implemented for Firefox 4.
- The remaining server side work is being done in
bug 459972
|Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 1.1 |
| Theme / Goal | Experience |
| Roadmap | Firefox Desktop |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | Silent Update |
| Engineering team | Release Engineering |
{{#set:Feature priority=P1
|Feature rank=1.1 |Feature theme=Experience |Feature roadmap=Firefox Desktop |Feature secondary roadmap=` |Feature list=Desktop |Feature project=Silent Update |Feature engineering team=Release Engineering }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | Test Plan |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=Test Plan |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}