Silent Update not now prompt: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 14: Line 14:
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation.  We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario.
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation.  We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario.
 
|Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version.  However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox.  
|Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version.  However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox.  


Line 22: Line 21:
There are a few things to note here:
There are a few things to note here:


#Both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully and Sandra is able to use the most secure, full-feature browser in the market.
#If both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened.
#Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will skip the update process this release and wait for the next release to update.
#Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks.  She has the option to "remind me later".
#This check will go on for Sandra for every Firefox release.  However, if she reaches 3 consecutive releases where 1 or more incompatible add-on does not become compatible in the 7 day grace period after the release date, Firefox will prompt Sandra and let her know that Firefox will be updated even with an incompatible add-on.   
#If she selects "remind me later", Firefox will defer for 7 additional days and on day 14, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible.  Firefox informs her that X add-ons were disabled due to security reasons.   


<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:
<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:
Line 34: Line 33:
#For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
#For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
#As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
#As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
#On the 7th day of the grace period if there are still incompatible Add-ons, we will skip updating the user for this release and wait for the N+1 release
#On the 7th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:
#For users who have incompatible Add-ons for 3 consecutive release, we will display the incompatible Add-on prompt on the 7th day of the 3rd release where they've had incompatible Add-ons and inform users that we are auto-updating them regardless of the incompatible Add-on (this has been approved by both Product and UX teams)
**"Update now" -- We ask users to update now and inform them that their browser is insecure and they are more vulnerable to attacks.  We will disable all incompatible add-ons (we will not remove them) at the time of updating.
#We will update today's incompatible Add-on prompt with a more positive tone (UX to provide specs below)
**"Remind me later" -- We will defer the update for one additional week and on day 14, we will update users automatically.  However, we will notify users that we will be disable X add-on due to security reasons.  (via drop-down or door hanger modules)
#The team is well aware this feels a bit heavy-handed, but we take security very seriously.  For users who still would like to control whether they are "auto-updated" when there are incompatible add-ons, the requirement here is to create an additional option within the pref menu to allow users to turn off "auto-updates for security reasons". 
#The UX team will follow-up with these requirements and provide visual specs on what the new prompt looks like and its exact behavior.
}}
}}
{{FeatureInfo
{{FeatureInfo

Revision as of 23:26, 21 November 2011

Please use "Edit with form" above to edit this page.

Status

Silent Update: Updated workflow for users with incompatible add-ons
Stage Definition
Status In progress
Release target `
Health OK
Status note Team met with UX to review use cases and the specs have been updated to reflect the latest plan.

{{#set:Feature name=Silent Update: Updated workflow for users with incompatible add-ons

|Feature stage=Definition |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Team met with UX to review use cases and the specs have been updated to reflect the latest plan. }}

Team

Product manager Chris Lee
Directly Responsible Individual Lawrence Mandel
Lead engineer Robert Strong
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Ioana Budnar
UX lead Alex Limi
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Chris Lee

|Feature feature manager=Lawrence Mandel |Feature lead engineer=Robert Strong |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Ioana Budnar |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Related to the Add-ons Compatibility Check feature, Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation. We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario.

2. Users & use cases

Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version. However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox.

Given there are incompatible add-ons, Firefox will not update Sandra to the latest version of Firefox and enter a 7 day grace period that will continue to check in the background if her incompatible add-ons become compatible.

There are a few things to note here:

  1. If both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened.
  2. Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks. She has the option to "remind me later".
  3. If she selects "remind me later", Firefox will defer for 7 additional days and on day 14, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible. Firefox informs her that X add-ons were disabled due to security reasons.

Things to note here -- the reason to go down the path of a "required" update is the following:

  1. Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox.
  2. To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward. All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated.
  3. Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience. Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.

3. Dependencies

`

4. Requirements

  1. All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date
  2. For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
  3. As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
  4. On the 7th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:
    • "Update now" -- We ask users to update now and inform them that their browser is insecure and they are more vulnerable to attacks. We will disable all incompatible add-ons (we will not remove them) at the time of updating.
    • "Remind me later" -- We will defer the update for one additional week and on day 14, we will update users automatically. However, we will notify users that we will be disable X add-on due to security reasons. (via drop-down or door hanger modules)
  1. The team is well aware this feels a bit heavy-handed, but we take security very seriously. For users who still would like to control whether they are "auto-updated" when there are incompatible add-ons, the requirement here is to create an additional option within the pref menu to allow users to turn off "auto-updates for security reasons".
  2. The UX team will follow-up with these requirements and provide visual specs on what the new prompt looks like and its exact behavior.

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=Related to the Add-ons Compatibility Check feature, Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation. We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario. |Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version. However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox.

Given there are incompatible add-ons, Firefox will not update Sandra to the latest version of Firefox and enter a 7 day grace period that will continue to check in the background if her incompatible add-ons become compatible.

There are a few things to note here:

  1. If both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened.
  2. Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks. She has the option to "remind me later".
  3. If she selects "remind me later", Firefox will defer for 7 additional days and on day 14, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible. Firefox informs her that X add-ons were disabled due to security reasons.

Things to note here -- the reason to go down the path of a "required" update is the following:

  1. Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox.
  2. To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward. All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated.
  3. Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience. Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.

|Feature dependencies=` |Feature requirements=#All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date

  1. For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
  2. As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
  3. On the 7th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:
    • "Update now" -- We ask users to update now and inform them that their browser is insecure and they are more vulnerable to attacks. We will disable all incompatible add-ons (we will not remove them) at the time of updating.
    • "Remind me later" -- We will defer the update for one additional week and on day 14, we will update users automatically. However, we will notify users that we will be disable X add-on due to security reasons. (via drop-down or door hanger modules)
  1. The team is well aware this feels a bit heavy-handed, but we take security very seriously. For users who still would like to control whether they are "auto-updated" when there are incompatible add-ons, the requirement here is to create an additional option within the pref menu to allow users to turn off "auto-updates for security reasons".
  2. The UX team will follow-up with these requirements and provide visual specs on what the new prompt looks like and its exact behavior.

|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 1.1
Theme / Goal Experience
Roadmap Firefox Desktop
Secondary roadmap `
Feature list Desktop
Project Silent Update
Engineering team Desktop front-end

{{#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=Desktop front-end }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance In progress 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=In progress |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=` }}


Retrieved from "https://wiki.allizom.org/index.php?title=Silent_Update_not_now_prompt&oldid=371915"