Revision as of 20:33, 13 October 2011

Features

Owner: Lawrence

Owner: Brian

Security review went well, new ideas for test cases, open issues like how do we handle crash reports
don't know how to store certificates to do updates - registry or settings file being acceptible
review notes linked in feature page
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
lawrence to follow up with chriss atlee
This change won't be visible by end users until release +1 as the service needs to be installed

Owner: Chris

Owner: Ehsan

Two options being considered, asked bsmedberg and a couple of other people for feedback
more than likely this will make 11
shouod hhave a better idea of when this can be done by next week
think should improve the linux and mac experience quite a bit

Owner: Rob to work with Asa.

Owner: Rob

12-24 hours, per session as when you exit your session you apply the update
if there's a newer udpate cancel the older update and download the newer one, this affects nightly and aurora, less important for release as the updates are every 6 week

have the ability to inform users via the know hour rights popup if we need to. curtis had a concern in being too silent.

@@ Line 31: / Line 31: @@
 ==Lessen the display of app update UI==
 Owner: Rob
+* 12-24 hours, per session as when you exit your session you apply the update
+* if there's a newer udpate cancel the older update and download the newer one, this affects nightly and aurora, less important for release as the updates are every 6 week
+*
 =Getting the word out=