Forum Discussion
Edge C release date - going out on a limb.
Drew1903 I honestly hope that they keep the canary and dev builds going even after full release. Because the browser, just like Chrome, can be installed and run from the user's contect (Windows Profile) there is no reason that you could not have the stable release version installed globally for all users of the PC, but had the Canary and / or Dev builds installed under your own context.
MSFT has been working for years on allowing two versions of a DLL to run side-by-side on the system, and I see no reason why you could not have two version of this new browser also running side-by-side on the same PC.
RORWessels
In the sense of Insider Builds, one can understand different 'levels'. Same as Win 10 Insider Builds has 3 Tracks AND Office Insiders has 3... depending on how frequently they receive changes & how stable they are. But, when it is a finished/released product and multiple Insider Builds are no longer being use or needing to be... how or why would there (still) be any scenario of running several versions simultaneously, anymore? I can see reason for Dev & Canary both, now, but, not later after Edge doesn't have Insider Builds & multiple Tracks anymore. But, certainly, maybe I'm missing something, here... 🤔
Cheers,
Drew
Drew1903: But, when it is a finished/released product and multiple Insider Builds are no longer being use or needing to be ...
If Microsoft elects to follow a rolling update model for updating Edge Chromium (Google Chrome auto-updates quite frequently, as does Firefox), Microsoft might want to keep a Insider test group in place to test the auto-updates on a wide variety of platforms before implementation. In that case, I can see a need for continuing testing channels after Edge Chromium is released. I don't know how Google handles auto-update testing, but Firefox has a user-testing group dedicated to testing auto-updates before implementation. What Microsoft does in this regard is up to Microsoft. But given the complexity of Windows 10, and the recent history of updates creating issues, it might be a good idea to keep a testing group in place after initial release.
Tom,
I am a Windows Insider. That program evolved w/ 10 being an on-going effort, so to speak. IF, Edge was going to continue constant work behind the scenes w/ Insiders, sure, then, one could opt to work on those Builds (as we are now) and in addition to simultaneously their daily-driver browser, Edge. Being open-source, this might be the case & w/ things being apps, really; it could potentially happen or be doable.
Otherwise, would be like the pre-10 days w/ OS beta testing. (Been there, done that). Meaning the betas are no more & new (GA) version replaces the old & is pushed out w/ the OS Update.
But, going back to paragraph 1, it could be both... Since Edge comes w/ the OS, it would be auto-updated AND a person may be able to, also, have & keeping working on (sending feedback) and running a beta version.
Cheers,
Drew- you don't know how Google handles auto-update testing? they have canary too and people can choose to download and test it.
it's so unstable though.HotCakeX you don't know how Google handles auto-update testing? they have canary too and people can choose to download and test it. it's so unstable though
Thanks for the information. I didn't know. I don't use Chrome at all, for a lot of reasons that aren't relevant to this forum, and I've never bothered to find out how they test updates.
