| Commit-Queue | +1 |
Hi David,
PTAL while I fix tests on Android/ChromeOS, thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thanks! I haven't yet looked at the tests :(
// Returns true if extensions should be enabled for users who were already
// signed in when they migrated to Dice.`existing signed-in users` makes more sense?
// existing sessions during Dice migration. In the new behavior, extensions`sync-to-signin migration`
!syncer::kExplicitSigninForExtensions.Get();What I understand is that now we are saving whether or not extensions and bookmarks sync was previously on. What I'd like to know is what will happen if some pre-M147 user in the original migration group jumps to M150 where our launch plan should already be complete? Or maybe, we plan to keep the experiment ongoing for a long time?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
!syncer::kExplicitSigninForExtensions.Get();What I understand is that now we are saving whether or not extensions and bookmarks sync was previously on. What I'd like to know is what will happen if some pre-M147 user in the original migration group jumps to M150 where our launch plan should already be complete? Or maybe, we plan to keep the experiment ongoing for a long time?
@dro...@chromium.org to correct if I am wrong.
The plan is to monitor that most of the 25% users in this bucket migrate to M147+ before shuffling groups, it is been discussed in the meeting that it could take around three weeks for like ~95% of the users to have migrated to M147. The threshold is not clear.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |