Open biancadanforth opened 4 years ago
I will help you with much of this, but we should keep it in mind.
en-us
locale, part of the Pioneer cohort, ... Most of these can be handled upstream by Normandy, but some may require the experiment code to check.about:addons
if the study is marked as hidden
. One option is a SUMO (support.mozilla.org) page referenced in the study's description in about:studies
.METRICS.md
(example) document for any telemetry you want to record.
Changelog for Additional considerations
[12/17/19]:
about:addons
if the study is marked as hidden
. One option is a SUMO (support.mozilla.org) page referenced in the study's description in about:studies
."
Engineering Review Checklist for Firefox WebExtension Experiments
This is a working checklist for reviewing WebExtension experiments in Firefox. Items may be added, edited or removed at any time.
README
:manifest.json
contains the following fields:name
version
author
description
homepage_url
incognito
(recommended value:"not_allowed"
)hidden
(value:true
)applications.gecko.id
(typically of the form"study-name@mozilla.org"
)applications.gecko.strict_min_version
(preferable)applications.gecko.strict_max_version
(preferable)[1]: As a reference, for a production application (i.e. not an experiment), a 2-3% worst case scenario regression in page load time would generally be considered acceptable. Since experiments are temporary and typically only go out to a very small percentage of users, we can often be more lenient.
Changelog for Engineering Checklist
[12/17/19]
manifest.json
contains the following fields:icons
("48"
and"96"
)hidden
, are no longer displayed inabout:addons
orabout:debugging
.incognito
keyhidden
keyabout:addons
andabout:debugging
after it is signed.