Firefox Core Engineering/App Updater roadmap: Difference between revisions
Jump to navigation
Jump to search
m (add "download") |
(Added PRD, tracking bug for Update Agent download phase) |
||
Line 12: | Line 12: | ||
== Milestones == | == Milestones == | ||
* "Update Agent" project was created from telemetry analysis. Phase 1 (download) should be completed by end of 2017 Q3 (target: FF58). | * "Update Agent" project was created from telemetry analysis. Phase 1 (download) should be completed by end of 2017 Q3 (target: FF58). | ||
** [https://docs.google.com/document/d/1vEgk70PQ4deqKlvIY5xN7clZeg8KnWVVFoeY2-eIEtc/edit PRD] | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1343671 Tracking bug] | |||
* From telemetry measurement and analysis additional cases should be handled similar to how the NS_ERROR_DOCUMENT_NOT_CACHED case is handled. Not scheduled and other work is currently a higher priority. (target: TBD) | * From telemetry measurement and analysis additional cases should be handled similar to how the NS_ERROR_DOCUMENT_NOT_CACHED case is handled. Not scheduled and other work is currently a higher priority. (target: TBD) | ||
* Create non-orphan dashboard for telemetry from "current" versions, analogous to [http://telemetry.mozilla.org/update-orphaning/ the update orphaning dashboard on t.m.o]. (target: Q3 2017) | * Create non-orphan dashboard for telemetry from "current" versions, analogous to [http://telemetry.mozilla.org/update-orphaning/ the update orphaning dashboard on t.m.o]. (target: Q3 2017) | ||
* <strike>Use LZMA for MAR file compression. This is based partially on telemetry measurement and analysis and specifically the time it takes to download. Should be completed by 2017 Q3 (target: FF56).</strike> '''completed: {{Bugzilla|641212}}''' | * <strike>Use LZMA for MAR file compression. This is based partially on telemetry measurement and analysis and specifically the time it takes to download. Should be completed by 2017 Q3 (target: FF56).</strike> '''completed: {{Bugzilla|641212}}''' | ||
* <strike>Use SHA384 certificates for MAR file signing. This is based on security analysis. Should be completed by 2017 Q3 (target: FF56).</strike> '''completed: {{Bugzilla|1324498}}''' | * <strike>Use SHA384 certificates for MAR file signing. This is based on security analysis. Should be completed by 2017 Q3 (target: FF56).</strike> '''completed: {{Bugzilla|1324498}}''' |
Revision as of 17:38, 19 October 2017
Application Update should be fast, reliable, and secure. It should also be unobtrusive and largely invisible to the user.
Strategy
- We need a regular cadence of measurement, analysis, and resultant code changes.
- Improve speed and reliability for known issues; continue investigations into unknown areas, because they yield positive changes.
Tactics
- Telemetry analysis and security analysis.
- Address testing gaps at the system level.
- Increase telemetry visibility for non-extreme use.
Milestones
- "Update Agent" project was created from telemetry analysis. Phase 1 (download) should be completed by end of 2017 Q3 (target: FF58).
- From telemetry measurement and analysis additional cases should be handled similar to how the NS_ERROR_DOCUMENT_NOT_CACHED case is handled. Not scheduled and other work is currently a higher priority. (target: TBD)
- Create non-orphan dashboard for telemetry from "current" versions, analogous to the update orphaning dashboard on t.m.o. (target: Q3 2017)
Use LZMA for MAR file compression. This is based partially on telemetry measurement and analysis and specifically the time it takes to download. Should be completed by 2017 Q3 (target: FF56).completed: 641212Use SHA384 certificates for MAR file signing. This is based on security analysis. Should be completed by 2017 Q3 (target: FF56).completed: 1324498