canmove, Confirmed users
312
edits
Firefox OS/Metrics: Difference between revisions
→Standardization of Device info
| Line 184: | Line 184: | ||
*There are two similar fields: os (GAIA version, "2.0.0.0") and software (GAIA distribution, "Boot2Gecko 2.0.0.0"). Only difference is a string added ahead of the software. What is the reason for needing two fields? | *There are two similar fields: os (GAIA version, "2.0.0.0") and software (GAIA distribution, "Boot2Gecko 2.0.0.0"). Only difference is a string added ahead of the software. What is the reason for needing two fields? | ||
*There does not seem to be a consistent identifier for 1.3T. Both 1.3 and 1.3T seem to have the same release number "1.3.0.0-prerelease". Why is that? | *There does not seem to be a consistent identifier for 1.3T. Both 1.3 and 1.3T seem to have the same release number "1.3.0.0-prerelease". Why is that? | ||
*Is update_channel being used? This is link to webpage for getting updates. historically this was used for "nightly", "stable" etc. | |||
There don't seem to be consistent identifiers for partner, OEM, and launch country in the FTU payload. Maybe we should include these explicitly, as we generally want to segment according to these variables. It appears that this done in some cases using update_channel (eg. "release-tcl-DT-DE"). Maybe we should formally use update_channel for this, standardizing it and including it in the certification (eg. "<release|prerelease>-<partner>-<oem>-<market>"). | Is this being used by customers? Currently, the examples are"release- | ||
**There don't seem to be consistent identifiers for partner, OEM, and launch country in the FTU payload. Maybe we should include these explicitly, as we generally want to segment according to these variables. It appears that this done in some cases using update_channel (eg. "release-tcl-DT-DE"). Maybe we should formally use update_channel for this, standardizing it and including it in the certification (eg. "<release|prerelease>-<partner>-<oem>-<market>"). | |||
* Otherwise, does update_channel represent something else that would be inconsistent with this scheme? | * Otherwise, does update_channel represent something else that would be inconsistent with this scheme? | ||