Firefox/Go Faster/Client Implementation Plan: Difference between revisions

Note about profile installs replacing the known-good set
(Wording)
(Note about profile installs replacing the known-good set)
Line 3: Line 3:
=Known-good sets=
=Known-good sets=


To reduce the number of possible configurations thus simplifying QA and dependency issues the client implementation uses the concept of a "known-good set" of system add-ons. This is a list of add-on IDs and versions to run for a particular application. The application will only run with a known-good set of system add-ons enabled or it will not enable any system add-ons and run standalone (we should generally never be in this state).
To reduce the number of possible configurations thus simplifying QA and dependency issues the client implementation uses the concept of a "known-good set" of system add-ons. This is a list of add-on IDs and versions to run for a particular application.


Every application package and update will be distributed with a known-good set of system add-ons for that application. Periodically the application will attempt to discover a new known-good set to be installed and used.
Every application package and update will be distributed with a known-good set of system add-ons for that application. Periodically the application will attempt to discover a new known-good set to be installed and used.
The application will only run with a known-good set of system add-ons enabled or it will not enable any system add-ons and run standalone though since the application ships with a known-good set we should generally never be in this state.
The only exception is in the case where a developer has installed a version of a system add-on in the profile for testing, in this case it essentially overrides the known-good version for that add-on.


=Running system add-ons=
=Running system add-ons=
canmove, Confirmed users
1,570

edits