We will tackle this bug after the 1st of February, 2021. That's the date when all of the `user` lifetime metrics we're aware of will expire (most of them being in [m-c]()). The decision was due to the following reasons: - hardcoding the list of know expirations in the code _right now_ doesn't buy us anything compared to waiting; - any expiration hardcoded in the SDK will work on "run time" date versus the "build time" expiration date we're using for all the metrics; - we need to disable adding expirations to 'user' lifetimes anyway (see bug 1626516); We can partially re-use what's in [this PR](https://github.com/mozilla/glean/pull/793) for removing the data from the expired metrics.
Bug 1604854 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We will tackle this bug after the 1st of February, 2021. That's the date when all of the `user` lifetime metrics we're aware of will expire (most of them being in [m-c](https://searchfox.org/mozilla-central/rev/a707541ff423ade0d81cef6488e6ecfa09273886/toolkit/components/telemetry/geckoview/streaming/metrics.yaml)). The decision was due to the following reasons: - hardcoding the list of know expirations in the code _right now_ doesn't buy us anything compared to waiting; - any expiration hardcoded in the SDK will work on "run time" date versus the "build time" expiration date we're using for all the metrics; - we need to disable adding expirations to 'user' lifetimes anyway (see bug 1626516); We can partially re-use what's in [this PR](https://github.com/mozilla/glean/pull/793) for removing the data from the expired metrics.