Forum Discussion
Edge GA Release Date
Drew1903 I don't know how accurate this information is, but Neowin reported yesterday ("https://www.neowin.net/news/microsoft039s-edge-chromium-browser-to-ship-in-windows-10-as-soon-as-it039s-generally-available", Rich Woods, Nov 5, 2019 17:46 EST) that:
"The next question is that of when the browser will actually ship with Windows 10, with many speculating that it might ship in 20H1 - which would be the first feature update after January 15 - or even 20H2, since 20H1 might RTM in December. As it turns out, neither of those theories are accurate, as the browser will start to be bundled with the OS right after the GA date.
"It's going to be a slow rollout though. We're not all going to wake up one day and find Legacy Edge replaced by the new Edge. That's how staged rollouts work though. There will be a small sample group that will get it first, and then that group will be expanded. As for new installations of Windows, the bits will be sent out to OEMs as soon as they're generally available."
- HotCakeXNov 06, 2019MVPLooks like it's their guess and they are not quoting any officials
- tomscharbachNov 06, 2019Bronze Contributor
HotCakeX "Looks like it's their guess and they are not quoting any officials."
I think that your caution is on target, and I appreciate the comment.
I agree with exercising caution when quoting the trade press, and that's why I opened with the caveat "I don't know how accurate this information is ..." Caution is doubly important, in this case, because the article does not attribute the information to Microsoft employees or Microsoft-published information.
As an aside, it seems to me that too many people fail to exercise necessary caution about "scoops" ( which might or might not be accurate) reported in the trade press.
As one example out of many, Windows Central recently published an article ("https://www.windowscentral.com/windows-10-os-development-schedule-changes", Zac Bowden, 28 October 2019).
The article does not identify the source of the information, so it might or might not be accurate.
Over the course of the last week, the "RTM in December" meme has been the subject of numerous articles in the trade press (OnMFST, TechRadar, Winbuzzer, WindowsLatest, and so on) all citing the Windows Central article but without any caveat about the accuracy/inaccuracy of the information. I've even seen the Windows Central article republished verbatim on a Windows 10 Insider forum without any qualification about the possible accuracy/inaccuracy of the information.
Speculation repeated often enough has a habit of morphing into "fact". In this case, as in the case of the "December RTM" reported by Windows Central, a healthy dose of caution is in order. I think that the best can be said is that both articles are consistent with other information Microsoft has released in the past**.
======================
**In the case of the "December RTM" article, past Microsoft announcements that the Windows 10 development/release schedules would be brought into line with Azure development/release schedules at some unspecified point in the future, and in the case of the article in question, past Microsoft announcements that Edge development/deployment cycles would follow Chromium/Chrome development cycles rather than Windows 10 development/upgrade cycles.
- BruceRobertsNov 06, 2019Steel Contributor
"The article does not identify the source of the information, so it might or might not be accurate."
It does, in the first paragraph.
- Drew1903Nov 06, 2019Silver Contributor
tomscharbach
Tom, I don't find any of that surprising or weird. Once thought it would be with 2003 (1) because I didn't reckon it could/would be ready & done before that and (2) because, it seemed logical, intuitive having it all come at the same time or motion.
And, it does follow, when Edge C goes GA, it would flip in the OS at that time. It's not tied to a major 6 month OS Update so, if Edge goes GA mid-Jan, in the OS would not need to be far behind, at all. Nor would it be unexpected for it not to be pushed out globally simultaneously.
IMO, it's silly mentioning 20H2. Edge C will be d'rigueur way, way before that... actually, it will be before 20H1. But, it's not bound to a Major 6 month Update, anyway, thus making that angle moot.
After so many release dates for a plethora of things... when we get it, we'll have it
Que sera, sera.
Cheers,
Drew- tomscharbachNov 06, 2019Bronze Contributor
Drew1903 "Tom, I don't find any of that surprising or weird."
I don't either, Drew. Although not confirmed by Microsoft, the Neowin speculation is consistent with past Microsoft statements about the development/deployment cycles for Edge Chromium.
- Drew1903Nov 06, 2019Silver Contributor
tomscharbach
Yes, Tom & the January 15th expected release date is from MS not, some outside source.
Cheers,
Drew
- HotCakeXNov 06, 2019MVPThe more they delay the integration the better. people expect a full featured browser. on the release date it won't be shipped with History or extension sync, nor will it have a proper inking for pdf and webpages. both of which are already available in Edge classic. If Microsoft integrates Edge 79, they will take away so many features from the users and it won't be good at all.