Forum Discussion
Dev channel update to 82.0.446.0 is live
AmineI whoops, that's my bad! The "Add all tabs to a new collection" feature is still under a controlled rollout, so not everybody has it yet. Usually I don't mention things until everybody has them, but this one slipped past me. It's something for everybody to look forward to though!
josh_bodner Thanks for the heads-up ! Controlled rollout, eh - hyped. Now I'll definitely check my context menu regularly for that option 
.
By the way, I've always wondered how/why these controlled rollouts were used in a test context. I see the point of controlled rollout for big releases, like Stable Windows 10's build updates, but I understand it less for features in an Insider build - been wondering that for a while, and not only regarding Edge Insider but also Windows Insider. Since we use an Insider channel, it should mean we're fine with testing, encountering and reporting issues & bugs, I believe.
Is it about user satisfaction ? Separating crashes due to the feature in testing and others ? Not sure honestly.
AmineI a lot of the theory behind rolling out features gradually is that, without a control population, you can't determine the causality of any regressions with any amount of certainty. In other words, if we unintentionally break something when we add a new feature, especially if it's something unrelated, we stand a much better chance of pinpointing it to being caused by the addition of that feature if there are still some people without that feature that we can compare to. Plus, having an off switch in general lets us turn things off when bad things happen, which has already proven useful a few times.
josh_bodner I see, thanks for your precisions 🙂 !
josh_bodner wrote:a lot of the theory behind rolling out features gradually is that, without a control population, you can't determine the causality of any regressions with any amount of certainty. In other words, if we unintentionally break something when we add a new feature, especially if it's something unrelated, we stand a much better chance of pinpointing it to being caused by the addition of that feature if there are still some people without that feature that we can compare to. Plus, having an off switch in general lets us turn things off when bad things happen, which has already proven useful a few times.
Can we control it client-side?
Can we control it client-side?
HotCakeX sometimes; not every feature is given a user-controllable flag, but can still be turned on or off server-side via a controlled rollout. In general, if it's behind a flag, that means it's not ready yet, and there's no way to know just how ready something is. It may be ready enough to be under a rollout already, or it may be so unstable that it causes you to crash on launch (I've learned that one the hard way). Plus, the more flags you turn on, the more likely you are to compound the instability.
