Data issues with cloned profiles

[Dave Townsend]

A new feature we are targetting for Firefox 60 involves giving each release
channel a separate profile by default. In order to push users into this
situation on upgrade non-release channels will make a clone of the release
profile for use going forwards. Currently this is a complete copy of all
files and settings from the release profile which raises a couple of
immediate potential issues:

The value of toolkit.telemetry.cachedClientID will be shared across
potentially many profiles. I could probably regenerate this for each cloned
profile if there is a procedure for doing this.

Any unsent pings will be cloned and so may be sent as duplications. The
only way to avoid this would be to not clone the ping but that might mean
that those pings are never sent. I'm not sure which is preferable.

Any other issues I'm not considering?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/fx-data-dev/attachments/20180205/a1ff521a/attachment.html>