Extension Manager:Projects:Confirm on Upgrade
Status
| Confirm add-ons on upgrade | |
| Stage | Landed |
| Status | Complete |
| Release target | Firefox 8 |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Confirm add-ons on upgrade
|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 8 |Feature health=OK |Feature status note=` }}
Team
| Product manager | Justin Scott |
| Directly Responsible Individual | Dave Townsend |
| Lead engineer | Dave Townsend |
| Security lead | Curtis Koenig |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Vlad Maniac |
| UX lead | Alex Faaborg |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | Unfocused, rs (available reviewers) |
{{#set:Feature product manager=Justin Scott
|Feature feature manager=Dave Townsend |Feature lead engineer=Dave Townsend |Feature security lead=Curtis Koenig |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Vlad Maniac |Feature ux lead=Alex Faaborg |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Unfocused, rs (available reviewers) }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Then next time existing users upgrade Firefox they should be presented with a list of add-ons they have installed where they can choose to disable them. By default add-ons from third-parties which may have been installed without the users' knowledge will be disabled. This replaces the compatibility wizard for that one time upgrade, subsequent upgrades use the compatibility wizard still.
This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)
2. Users & use cases
Goals
- Do compatibility and update checks for all installed extensions
- Show users a list of installed extensions
- Allow disabling extensions before startup
Use cases
- User with no installed add-ons
- Should not see any UI on startup
- User who hasn't manually installed add-ons but has some installed by a third-party app
- If any add-ons are enabled user will periodically see the list of add-ons
- User can choose which of the add-ons to keep enabled, by default all will be disabled
- User who has only manually installed add-ons
- If any add-ons are enabled user will periodically see the list of add-ons
- User can choose which of the add-ons to keep enabled, by default none will be disabled
- Any available updates for add-ons will be installed if automatic installation is enabled
- User has both manually installed and third-party installed add-ons
- If any add-ons are enabled user will periodically see the list of add-ons
- User can choose which of the add-ons to keep enabled, by default the third-party installed add-ons will be disabled
- Any available updates for the manually installed add-ons will be installed if automatic installation is enabled
3. Dependencies
`
4. Requirements
- Developed UI must pass UI review
- Feature should be covered by automated tests
Non-goals
`
Stage 2: Design
5. Functional specification
These are the different states that an add-on can be in and what message we should show in the action column for them.
In all cases if an update is available and automatic updating is enabled then the update is installed (even though in some cases that isn't mentioned in the action message).
If an update is available and automatic updating is disabled then if the user doesn't want the add-on the update is never offered, if the user wants to keep the add-on then the user has the option to install the update (which in some cases is required for the add-on to work).
| Was active | Is compatible | Update available | User keeps | User disables |
|---|---|---|---|---|
| No | No | No | "will be enabled when compatible" | -- |
| No | No | Automatic | "will be updated to be compatible" | -- |
| No | No | Manual | "update to make compatible" (checkbox) | -- |
| No | Yes | No | -- | -- |
| No | Yes | Automatic | -- | -- |
| No | Yes | Manual | "optional update" (checkbox) | -- |
| Yes | No | No | "will be enabled when compatible" | "will be disabled" |
| Yes | No | Automatic | "will be updated to be compatible" | "will be disabled" |
| Yes | No | Manual | "update to make compatible" (checkbox) | "will be disabled" |
| Yes | Yes | No | -- | "will be disabled" |
| Yes | Yes | Automatic | -- | "will be disabled" |
| Yes | Yes | Manual | "optional update" (checkbox) | "will be disabled" |
6. User experience design
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
- No formal security review necessary.
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=Then next time existing users upgrade Firefox they should be presented with a list of add-ons they have installed where they can choose to disable them. By default add-ons from third-parties which may have been installed without the users' knowledge will be disabled. This replaces the compatibility wizard for that one time upgrade, subsequent upgrades use the compatibility wizard still.
This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)
|Feature users and use cases===== Goals ====
- Do compatibility and update checks for all installed extensions
- Show users a list of installed extensions
- Allow disabling extensions before startup
Use cases
- User with no installed add-ons
- Should not see any UI on startup
- User who hasn't manually installed add-ons but has some installed by a third-party app
- If any add-ons are enabled user will periodically see the list of add-ons
- User can choose which of the add-ons to keep enabled, by default all will be disabled
- User who has only manually installed add-ons
- If any add-ons are enabled user will periodically see the list of add-ons
- User can choose which of the add-ons to keep enabled, by default none will be disabled
- Any available updates for add-ons will be installed if automatic installation is enabled
- User has both manually installed and third-party installed add-ons
- If any add-ons are enabled user will periodically see the list of add-ons
- User can choose which of the add-ons to keep enabled, by default the third-party installed add-ons will be disabled
- Any available updates for the manually installed add-ons will be installed if automatic installation is enabled
|Feature dependencies=` |Feature requirements=* Developed UI must pass UI review
- Feature should be covered by automated tests
|Feature non-goals=` |Feature functional spec=These are the different states that an add-on can be in and what message we should show in the action column for them.
In all cases if an update is available and automatic updating is enabled then the update is installed (even though in some cases that isn't mentioned in the action message).
If an update is available and automatic updating is disabled then if the user doesn't want the add-on the update is never offered, if the user wants to keep the add-on then the user has the option to install the update (which in some cases is required for the add-on to work).
| Was active | Is compatible | Update available | User keeps | User disables |
|---|---|---|---|---|
| No | No | No | "will be enabled when compatible" | -- |
| No | No | Automatic | "will be updated to be compatible" | -- |
| No | No | Manual | "update to make compatible" (checkbox) | -- |
| No | Yes | No | -- | -- |
| No | Yes | Automatic | -- | -- |
| No | Yes | Manual | "optional update" (checkbox) | -- |
| Yes | No | No | "will be enabled when compatible" | "will be disabled" |
| Yes | No | Automatic | "will be updated to be compatible" | "will be disabled" |
| Yes | No | Manual | "update to make compatible" (checkbox) | "will be disabled" |
| Yes | Yes | No | -- | "will be disabled" |
| Yes | Yes | Automatic | -- | "will be disabled" |
| Yes | Yes | Manual | "optional update" (checkbox) | "will be disabled" |
|Feature ux design=* Design mockup |Feature implementation plan=` |Feature security review=* No formal security review necessary. |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* bug 596343 |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Add-ons |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | Desktop front-end |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Add-ons |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}
Team status notes
| status | notes | |
| Products | Pending blog post | ` |
| Engineering | ` | ` |
| Security | pass | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | active | Test Plan |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=Pending blog post
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=pass |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=active |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=` }}