Program Management/Programs/Silent Update/2011-10-13: Difference between revisions

← Older edit

Program Management/Programs/Silent Update/2011-10-13 (view source)

Revision as of 20:49, 13 October 2011

1,191 bytes added , 13 October 2011

→‎Removal of OS security dialog for Windows

LawrenceMandel

Confirmed users

2,473

edits

@@ Line 3: / Line 3: @@
 ==Lessen the showing of the what's new page==
 Owner: Lawrence
+* We landed this change for 8. Great work.
+* Change allows to show or hide the what's new page.
+* Will show the what's new page for users moving up from 3.6 but not for users moving up from 7.
 ==Removal of OS security dialog for Windows==
 Owner: Brian
-* Security review went well, new ideas for test cases, open issues like how do we handle crash reports
+* Security review went well ([[Security/Reviews/Firefox10/SilentUpdateOSDialogs |review notes]])
-* don't know how to store certificates to do updates - registry or settings file being acceptible
+** New ideas for test cases.
-* review notes linked in feature page
+** Open issues like how do we handle crash reports.
-* needs to land on nightly, blocked - need to wait for driver signing before we can land it, can land code but can't turn it on beforehand
+* Don't know how to store certificates to do updates - need to find out if  a registry or settings file will be acceptable
-* lawrence to follow up with chriss atlee
+* This feature needs to land on nightly.
-* This change won't be visible by end users until release +1 as the service needs to be installed
+* Currently blocked by {{bug|663055}} - need to wait for driver signing before we can land it, can land code but can't turn it on beforehand
+** Lawrence to follow-up with Chris Atlee
+* This change won't be visible by end users until release +1 as the service needs to be installed. This means if it ships in FF10, users won't see the results of this change until FF11.
 ==Add-ons Default to Compatible==
 Owner: Chris
+* Met with Justin Scott and team yesterday.
+* Work prioritized. Earliest we'll start to see changes that can land is 3 weeks.
 ==Apply update on shutdown==
 Owner: Ehsan
-* Two options being considered, asked bsmedberg and a couple of other people for feedback
+* Two options being considered, review and comment in [[Background_Updates/Implementation_Strategies | Implementation Strategies wiki page]].
-* more than likely this will make 11
+** Asked bsmedberg and a couple of other people for feedback.
-* shouod hhave a better idea of when this can be done by next week
+* More than likely this will make FF11.
-* think should improve the linux and mac experience quite a bit
+* Should have a better idea of when this can be done by next week.
+* Think that this should improve the Linux and Mac experience quite a bit.
 ==New workflow for updating users with incompatible add-ons==
 Owner: Rob to work with Asa.
-* need meeting with ux to ensure that the experience is acceptible
+* Need a meeting with UX to ensure that the experience is acceptable
-* should we ignore the fact that they have incompatible add-ons?
+* Should we ignore the fact that they have incompatible add-ons?
-* some ui would need to be included to allow users to override our override
+* Some UI would need to be included to allow users to override our override.
 ==Lessen the display of app update UI==
 Owner: Rob
+* Landed change for display delay from 12 to 24 hours in FF8.
+** Delay is per session as when you exit your session you apply the update.
+* Remaining work
+** If there's a newer update we should cancel the older update and download the newer one, this affects nightly and aurora and is less important for release as the updates are every 6 weeks.
 =Getting the word out=
@@ Line 39: / Line 51: @@
 ** [http://www.geek.com/articles/news/firefox-to-get-optional-silent-updates-2011105/ Geek.com - Firefox to get optional silent updates]
 ** [http://www.favbrowser.com/silent-updates-coming-to-firefox-after-all/ FavBrowser - Silent Updates Coming To Firefox After All]
+* To increase exposure Lawrence listed silent update work on the planning call this week. Will add to development call next week as well.
 =Other=
-have the ability to inform users via the know hour rights popup if we need to. curtis had a concern in being too silent.
+* Curtis raised a concern over the updates being too silent. We have the ability to inform users via the "know your rights" popup if we need to. We can investigate further if required.