Create an about:flag multi-state setting to control Chrome Content Suggestions |
||||||||||||
Issue descriptionWith more content suggestion experiments coming up and features being in different stages, we should have flag to better support review situations: Chrome Content Suggestion Features Overrides settings and experiments related to Chrome Content Suggestion features. - Default: no overrides - All experimental features: enables all experimental features - Beta features for review: only launched features and "enabled by default" - Stable features: only launched or launch approved features
,
Aug 5 2016
,
Aug 8 2016
Discussed offline with Patrick. Probably too complicated to rush it for M54. For the time being we keep specific finch features and about:flags entries per Zine section (such as articles for you, bookmarks, offline pages, ...). All these features should always stay DISABLED_BY_DEFAULT. Via Finch, one can set per feature that it is - ready for the prime time (= up for review) (by flipping it on for canary/dev) - approved by reviews (by flipping it on for beta/stable) For M55, we want to have the "master switch" as explained above. - We would keep the per-section features in place to have fine-grained control of what is displayed by default in individual channels. - The "ready for the prime time" bit per feature would be inferred from the per-section feature state (this allows us to kill some feature remotely) - On top of that, the master switch needs to know a list of features that are launch reviewed (probably passed serialized in a variation param of the new master switch feature). - Maybe we need another list of features that are not yet ready for the prime time but should already appear in the "All experimental features" variation. Open questions: - There would be server-passed variation params and a client side variation param (all experiments / beta features / stable features). Currently we do not merge these two list of params (and only take the local list from about:flags). Merging might be complicated. Is there some work around?
,
Aug 16 2016
,
Aug 16 2016
Patrick, what do I need to change so that the bug does not appear on the Zine dashboard (as it is M55 bug, now)?
,
Aug 18 2016
The dashboard doesn't know milestone labels. But we could move it to another feature version. Anyways, this is off topic. Reach out to me via email if you want to learn more.
,
Oct 17 2016
,
Oct 20 2016
,
Oct 26 2016
,
Nov 15 2016
moving to M-57 and lowering prio
,
Nov 22 2016
,
Nov 23 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 27 2017
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by finkm@google.com
, Aug 1 2016