Firefox Core Engineering/App Updater roadmap: Difference between revisions

m
reduce outlining
(created)
 
m (reduce outlining)
Line 1: Line 1:
== Application Update Roadmap ==
Application Update should be fast, reliable, and secure. It should also be unobtrusive and largely invisible to the user.
Application Update should be fast, reliable, and secure. It should also be unobtrusive and largely invisible to the user.


=== Strategy ===
== Strategy ==
* We need a regular cadence of measurement, analysis, and resultant code changes.
* 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.
* Improve speed and reliability for known issues; continue investigations into unknown areas, because they yield positive changes.


=== Tactics ===
== Tactics ==
* Telemetry analysis and security analysis.
* Telemetry analysis and security analysis.
* Address testing gaps at the system level.
* Address testing gaps at the system level.
* Increase telemetry visibility for non-extreme use.
* Increase telemetry visibility for non-extreme use.


=== Milestones ===
== Milestones ==
* "Update Agent" project was created from telemetry analysis. Phase 1 should be completed by end of 2017 Q3 (target: FF58).
* "Update Agent" project was created from telemetry analysis. Phase 1 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)
* 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)
Confirmed users
745

edits