Forum Discussion
josh_bodner
Microsoft
Apr 14, 2020Dev channel update to 83.0.478.5 is live
Hello insiders, today we’re releasing build 83.0.478.5 to the Dev channel. This is our Beta release candidate for major version 83, and since it’s also not that much newer than last week’s Dev chann...
Ed Sparks
Apr 15, 2020Iron Contributor
It would be great if you could address the ongoing frustration that is Controlled Feature Rollouts.
As a start if you could please indicate every time in these release notes when this applies, and to which markets or regions, etc.
Secondly please up the speed at which you then release these features, or better yet just can this entire concept for Dev and Canary builds.
We're here to test the browser and live on the cutting edge. Often these features get announced and don't show up for several weeks, if seemingly ever. By then they're often completely forgotten about and aren't well tested by the user community. It's still not clear what the point of this is in these testing release channels?
Thanks for the great work otherwise Edge Team!
josh_bodner
Microsoft
Apr 15, 2020Ed Sparks in general, I try not to mention new features here in the release notes until they're turned on via code, and thus not with a controlled rollout. Or if there is a new feature only available via a controlled rollout, but it's something we want to make people aware of before everybody has it, I usually try to mention that it's under a rollout. Unfortunately, I quite often make mistakes, since I look primarily at code changes.
I think one thing that hasn't been communicated well, though, is just how important controlled rollouts are for assuring we don't regress any of our fundamentals: reliability, performance, etc. Often, when we introduce new code, it can have unforeseen consequences in completely unrelated areas, and having control populations to compare against is crucial for being able to quickly find and root-cause those issues. While it's our goal to only take a couple of weeks for this process, you're right that it often takes us longer before we enable the feature for everybody via code, so we have room for improvement there.