[tracking bug::UserConsent] Post launch cleanup |
|||||||||||
Issue descriptionCurrently we have 2 implementations to submit user consents (through user events and through a separate datatype). We want to fully migrate to the separate datatype. I've discussed with markusheintz@ and we are not aware of any issue with the new datatype in M69. Thus, I can start cleaning up the old implementation. I will wait for M71 BP to pass. ⛆ |
|
|
,
Oct 15
The NextAction date has arrived: 2018-10-15
,
Nov 6
,
Nov 15
,
Nov 15
,
Nov 15
,
Nov 15
I had a look, created more bugs and close obsolete ones. If I were doing this, I would do the following: 0) Remove TODO about garbage collection from both Consent and UserEvents code ( issue 851439 ). 1) Delete the enabled-dy-default feature gating the new datatype ( issue 905636 ). 2) Remove consents logic from user events code. This will involve factories as well, I am not sure whether this could be broken down into multiple CLs. It may be possible to deprecate some fields in protos as well. ( issue 905639 ) 3) Rewrite and reenable user event web browser test. Also add a similar test for UserConsents datatype. (issue 843847) 4) Improve mess with dependencies (issue 850428).
,
Nov 15
If you need any help, please ask! Thank you!
,
Nov 21
I'll give this a shot.
,
Nov 27
I think we can close the tracking bug. There's still bug 843847 (originally about a flaky test which has since been removed, now repurposed to possibly adding some additional tests), and bug 850428 about a dependency cycle which is being actively addressed. |
||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by vitaliii@chromium.org
, Oct 4Summary: [tracking bug::UserConsent] Post launch cleanup (was: [UserConsent] Post launch cleanup)