Silent Update
Status
| Silent Update | |
| Stage | Planning |
| Status | In progress |
| Release target | ` |
| Health | OK |
| Status note | Master feature page for all components that are required to deliver a "silent update" experience to users. |
{{#set:Feature name=Silent Update
|Feature stage=Planning |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Master feature page for all components that are required to deliver a "silent update" experience to users. }}
Team
| Product manager | Chris Lee |
| Directly Responsible Individual | Chris Lee |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Chris Lee
|Feature feature manager=Chris Lee |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
=== This feature falls under the Experience theme.
With the transition to the Rapid Release development model, the frequency in which we interrupt a user's workflow will be increasingly more common. With goals to offer a secure, feature-rich, and fun browsing experience, we want to ensure everyone is on the latest version of Firefox. To achieve this goal, this particular feature will breakdown the necessary pieces to deliver a silent update experience. ===
Silent Update is comprised of the following 6 components:
1) Move bulk of update to background before shut down and remove update UI from browser start-up. (feature page):
- Updater will need to change for Windows, Mac and Linux
2) Add-on compatibility check will default to compatible (feature page):
- Modifying how Firefox determines which Add-ons are compatible
- This will exclude:
- All non-binary component add-ons
- All strict incompatible add-ons
- All blacklisted add-ons
3) What's new page content will transition to other tools and what's new tab will be removed (feature page):
- Dedicated placement in Firefox about:home page (being explored)
- Hover panel from from somewhere on the page (being explored)
- Brainstorm with UX/Marketing
4) Firefox updates need to bypass OS permissions dialog (feature page):
- Win7 UAC (user account control) dialogue
- Mac OS: determine if there are issues for non-admins
5) Update the add-on compatibility check prompt (feature page):
- In conjunction with component (2), when the update process encounters an incompatible add-on we should prompt with a dialog providing users the options of "not now" or "remind me later".
2. Users & use cases
`
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
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==== This feature falls under the Experience theme.
With the transition to the Rapid Release development model, the frequency in which we interrupt a user's workflow will be increasingly more common. With goals to offer a secure, feature-rich, and fun browsing experience, we want to ensure everyone is on the latest version of Firefox. To achieve this goal, this particular feature will breakdown the necessary pieces to deliver a silent update experience. ===
Silent Update is comprised of the following 6 components:
1) Move bulk of update to background before shut down and remove update UI from browser start-up. (feature page):
- Updater will need to change for Windows, Mac and Linux
2) Add-on compatibility check will default to compatible (feature page):
- Modifying how Firefox determines which Add-ons are compatible
- This will exclude:
- All non-binary component add-ons
- All strict incompatible add-ons
- All blacklisted add-ons
3) What's new page content will transition to other tools and what's new tab will be removed (feature page):
- Dedicated placement in Firefox about:home page (being explored)
- Hover panel from from somewhere on the page (being explored)
- Brainstorm with UX/Marketing
4) Firefox updates need to bypass OS permissions dialog (feature page):
- Win7 UAC (user account control) dialogue
- Mac OS: determine if there are issues for non-admins
5) Update the add-on compatibility check prompt (feature page):
- In conjunction with component (2), when the update process encounters an incompatible add-on we should prompt with a dialog providing users the options of "not now" or "remind me later".
|Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |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 | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | Desktop front-end |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| 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=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}