Home

Edge GA Release Date

%3CLINGO-SUB%20id%3D%22lingo-sub-985268%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985268%22%20slang%3D%22en-US%22%3E2003%20is%2Fwas%20the%20probable%20Windows%2010%20build%20number%20for%20Edge%20insider%20to%20be%20intergrated%20into%20the%20OS%2C%20the%20release%20date%20of%20course%20was%20always%20different%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-985981%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985981%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316824%22%20target%3D%22_blank%22%3E%40Drew1903%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3E%3CEM%3EApparently%2C%20we%20are%20not%20waiting%20until%202003%20(Update)%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20it%20looks%20like%2020H1%20is%20going%20to%20RTM%20in%20December%20and%20since%20(as%20I%20understand%20it)%2020H1%20has%20not%20yet%20embedded%20Edge%20Chromium%20into%20the%20release%2C%20my%20guess%20is%20that%20Microsoft%20will%20embed%20Edge%20Chromium%20into%20Windows%2010%20as%20part%20of%20a%20monthly%20update%20sometime%20during%202020%20or%20wait%20until%2020H2.%26nbsp%3B%20Microsoft%20hasn't%20said%20anything%20about%20it%20yet%2C%20though%2C%20as%20far%20as%20I%20know%2C%20so%20your%20guess%20is%20as%20good%20as%20mine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVersion%2079.0.309.nn%20is%20the%20release%20candidate%20for%20January%2015%2C%20and%20when%20that%20has%20been%20released%2C%20then%20Microsoft%20will%20probably%20follow%20the%20Chromium%20development%2Frelease%20cycle%2C%20updating%20every%20six%20weeks%20or%20so%20going%20forward.%26nbsp%3B%20Microsoft%20%3CEM%3Ehas%3C%2FEM%3E%20said%20that%20Edge%20Chromium%20updates%20will%20not%20be%20tied%20to%20the%20Windows%2010%20update%20cycle.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-986443%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-986443%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ETom%2C%20some%20suggested%20%26amp%3B%20thought%2C%20including%20myself%2C%20that%20the%20%3CSTRONG%3EGA%3C%2FSTRONG%3E%20for%20Edge%20C%20would%2C%20maybe%2C%20come%20with%20the%20Spring%202020%20Update%20for%20Win10%20(2003).%26nbsp%3B%20Seemed%20that%20might%20allow%20enough%20time%20to%20have%20the%20thing%20done%3B%20feels%20like%20there%2C%20still%2C%20is%20much%20to%20be%20done.%26nbsp%3B%20But%2C%20MS%20say%20it%20is%20expecting%20to%20release%20it%20mid-January.%26nbsp%3B%20So%2C%20that%20would%2C%20indeed%2C%20suggest%20Edge%20stuff%20is%20not%20tied%20to%20the%20'every%206%20months'%20major%20Updates%20of%20Win10.%3CBR%20%2F%3E%3CBR%20%2F%3ERight%20now%2C%20Insider%20Builds%20have%20the%20same%20opportunity%20to%20run%20Edge%20(beta)%20Channels.%26nbsp%3B%20Once%20(new)%20Edge%20is%20embedded%20in%20the%20OS%2C%20it%20will%20be%20in%20the%20Insider%20Builds%2C%20too.%26nbsp%3B%20That's%20my%20'guess'%2C%20anyway.%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20can%20be%20awkward%20trying%20to%20guess%20at%20things%20outside%20of%20Insider%20Builds%20by%20looking%20at%20what%20Insider%20Builds%20are%20doing%3B%20can%20be%20way%20out%20of%20sync%20with%20each%20other...%20especially%20when%20Fast%20Track%20%26amp%3B%20Skip%20Ahead%20split.%3CBR%20%2F%3E%3CBR%20%2F%3EBut%2C%20I'm%20sticking%20to%20the%20notion%20that%20once%20it's%20GA%2C%20we'll%20see%20it%20in%20the%20Insider%20Builds%2C%20too.%20Then%20it's%2C%20actually%2C%20truly%2C%20part%20of%20the%20OS.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-987250%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-987250%22%20slang%3D%22en-US%22%3EI%20hope%20not..I'm%20on%20insider%20and%20I%20still%20enjoy%20Edge%20classic.%20the%20new%20Edge%20would%20just%20be%20useless%20for%20me%20since%20I%20use%20Canary%20and%20it%20has%20more%20features%20than%20stable%20build.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-987607%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-987607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316824%22%20target%3D%22_blank%22%3E%40Drew1903%3C%2FA%3E%26nbsp%3B%20I%20don't%20know%20how%20accurate%20this%20information%20is%2C%20but%20Neowin%20reported%20yesterday%20(%22%3CA%20href%3D%22https%3A%2F%2Fwww.neowin.net%2Fnews%2Fmicrosoft039s-edge-chromium-browser-to-ship-in-windows-10-as-soon-as-it039s-generally-available%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft's%20Edge%20Chromium%20browser%20to%20ship%20in%20Windows%2010%20as%20soon%20as%20it's%20generally%20available%3C%2FA%3E%22%2C%26nbsp%3BRich%20Woods%2C%20Nov%205%2C%202019%2017%3A46%20EST)%20that%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CEM%3EThe%20next%20question%20is%20that%20of%20when%20the%20browser%20will%20actually%20ship%20with%20Windows%2010%2C%20with%20many%20speculating%20that%20it%20might%20ship%20in%2020H1%20-%20which%20would%20be%20the%20first%20feature%20update%20after%20January%2015%20-%20or%20even%2020H2%2C%20since%2020H1%20might%20RTM%20in%20December.%20As%20it%20turns%20out%2C%20neither%20of%20those%20theories%20are%20accurate%2C%20as%20the%20browser%20will%20start%20to%20be%20bundled%20with%20the%20OS%20right%20after%20the%20GA%20date.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%22It's%20going%20to%20be%20a%20slow%20rollout%20though.%20We're%20not%20all%20going%20to%20wake%20up%20one%20day%20and%20find%20Legacy%20Edge%20replaced%20by%20the%20new%20Edge.%20That's%20how%20staged%20rollouts%20work%20though.%20There%20will%20be%20a%20small%20sample%20group%20that%20will%20get%20it%20first%2C%20and%20then%20that%20group%20will%20be%20expanded.%20As%20for%20new%20installations%20of%20Windows%2C%20the%20bits%20will%20be%20sent%20out%20to%20OEMs%20as%20soon%20as%20they're%20generally%20available.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-987645%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-987645%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ETom%2C%20I%20don't%20find%20any%20of%20that%20surprising%20or%20weird.%26nbsp%3B%20Once%20thought%20it%20would%20be%20with%202003%20(1)%20because%20I%20didn't%20reckon%20it%20could%2Fwould%20be%20ready%20%26amp%3B%20done%20before%20that%20and%20(2)%20because%2C%20it%20seemed%20logical%2C%20intuitive%20having%20it%20all%20come%20at%20the%20same%20time%20or%20motion.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%2C%20it%20does%20follow%2C%20when%20Edge%20C%20goes%20GA%2C%20it%20would%20flip%20in%20the%20OS%20at%20that%20time.%26nbsp%3B%20It's%20not%20tied%20to%20a%20major%206%20month%20OS%20Update%20so%2C%20if%20Edge%20goes%20GA%20mid-Jan%2C%20in%20the%20OS%20would%20not%20need%20to%20be%20far%20behind%2C%20at%20all.%26nbsp%3B%20Nor%20would%20it%20be%20unexpected%20for%20it%20not%20to%20be%20pushed%20out%20globally%20simultaneously.%3CBR%20%2F%3E%3CBR%20%2F%3EIMO%2C%20it's%20silly%20mentioning%2020H2.%26nbsp%3B%20Edge%20C%20will%20be%20d'rigueur%20way%2C%20way%20before%20that...%20actually%2C%20it%20will%20be%20%3CEM%3Ebefore%3C%2FEM%3E%2020H1.%20But%2C%20it's%20not%20bound%20to%20a%20Major%206%20month%20Update%2C%20anyway%2C%20thus%20making%20that%20angle%20moot.%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20so%20many%20release%20dates%20for%20a%20plethora%20of%20things...%20when%20we%20get%20it%2C%20we'll%20have%20it%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Flaugh_40x40.gif%22%20alt%3D%22%3Alol%3A%22%20title%3D%22%3Alol%3A%22%20%2F%3E%26nbsp%3BQue%20sera%2C%20sera.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-987762%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-987762%22%20slang%3D%22en-US%22%3ELooks%20like%20it's%20their%20guess%20and%20they%20are%20not%20quoting%20any%20officials%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-987813%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-987813%22%20slang%3D%22en-US%22%3EThe%20more%20they%20delay%20the%20integration%20the%20better.%20people%20expect%20a%20full%20featured%20browser.%20on%20the%20release%20date%20it%20won't%20be%20shipped%20with%20History%20or%20extension%20sync%2C%20nor%20will%20it%20have%20a%20proper%20inking%20for%20pdf%20and%20webpages.%20both%20of%20which%20are%20already%20available%20in%20Edge%20classic.%20If%20Microsoft%20integrates%20Edge%2079%2C%20they%20will%20take%20away%20so%20many%20features%20from%20the%20users%20and%20it%20won't%20be%20good%20at%20all.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-988053%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-988053%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%20%22%3CEM%3ELooks%20like%20it's%20their%20guess%20and%20they%20are%20not%20quoting%20any%20officials.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20that%20your%20caution%20is%20on%20target%2C%20and%20I%20appreciate%20the%20comment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20agree%20with%20exercising%20caution%20when%20quoting%20the%20trade%20press%2C%20and%20that's%20why%20I%20opened%20with%20the%20caveat%20%22%3CEM%3EI%20don't%20know%20how%20accurate%20this%20information%20is%20...%3C%2FEM%3E%22%26nbsp%3B%20Caution%20is%20doubly%20important%2C%20in%20this%20case%2C%20because%20the%20article%20does%20not%20attribute%20the%20information%20to%20Microsoft%20employees%20or%20Microsoft-published%20information.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20an%20aside%2C%20it%20seems%20to%20me%20that%20too%20many%20people%20fail%20to%20exercise%20necessary%20caution%20about%20%22scoops%22%20(%20which%20might%20or%20might%20not%20be%20accurate)%20reported%20in%20the%20trade%20press.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20one%20example%20out%20of%20many%2C%20Windows%20Central%20recently%20published%20an%20article%20(%22%3CA%20href%3D%22https%3A%2F%2Fwww.windowscentral.com%2Fwindows-10-os-development-schedule-changes%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft's%20Windows%2010%2020H1%20release%20will%20be%20first%20to%20RTM%20in%20December%20under%20Azure%20schedule%3C%2FA%3E%22%2C%20Zac%20Bowden%2C%2028%20October%202019).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20article%20does%20not%20identify%20the%20source%20of%20the%20information%2C%20so%20it%20might%20or%20might%20not%20be%20accurate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOver%20the%20course%20of%20the%20last%20week%2C%20the%20%22RTM%20in%20December%22%20meme%20has%20been%20the%20subject%20of%20numerous%20articles%20in%20the%20trade%20press%20(OnMFST%2C%20TechRadar%2C%20Winbuzzer%2C%20WindowsLatest%2C%20and%20so%20on)%20all%20citing%20the%20Windows%20Central%20article%20but%20without%20any%20caveat%20about%20the%20accuracy%2Finaccuracy%20of%20the%20information.%20I've%20even%20seen%20the%20Windows%20Central%20article%20republished%20verbatim%20on%20a%20Windows%2010%20Insider%20forum%20without%20any%20qualification%20about%20the%20possible%20accuracy%2Finaccuracy%20of%20the%20information.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESpeculation%20repeated%20often%20enough%20has%20a%20habit%20of%20morphing%20into%20%22fact%22.%20In%20this%20case%2C%20as%20in%20the%20case%20of%20the%20%22December%20RTM%22%20reported%20by%20Windows%20Central%2C%20a%20healthy%20dose%20of%20caution%20is%20in%20order.%20I%20think%20that%20the%20best%20can%20be%20said%20is%20that%20both%20articles%20are%20consistent%20with%20other%20information%20Microsoft%20has%20released%20in%20the%20past**.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E**In%20the%20case%20of%20the%20%22December%20RTM%22%20article%2C%20past%20Microsoft%20announcements%20that%20the%20Windows%2010%20development%2Frelease%20schedules%20would%20be%20brought%20into%20line%20with%20Azure%20development%2Frelease%20schedules%20at%20some%20unspecified%20point%20in%20the%20future%2C%20and%20in%20the%20case%20of%20the%20article%20in%20question%2C%20past%20Microsoft%20announcements%20that%20Edge%20development%2Fdeployment%20cycles%20would%20follow%20Chromium%2FChrome%20development%20cycles%20rather%20than%20Windows%2010%20development%2Fupgrade%20cycles.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-988082%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-988082%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316824%22%20target%3D%22_blank%22%3E%40Drew1903%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3E%3CEM%3ETom%2C%20I%20don't%20find%20any%20of%20that%20surprising%20or%20weird.%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20don't%20either%2C%20Drew.%26nbsp%3B%20Although%20not%20confirmed%20by%20Microsoft%2C%20the%20Neowin%20speculation%20is%20consistent%20with%20past%20Microsoft%20statements%20about%20the%20development%2Fdeployment%20cycles%20for%20Edge%20Chromium.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-988273%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-988273%22%20slang%3D%22en-US%22%3EI%20think%20people%20take%20articles%20from%20Windows%20central%20for%20granted%20because%20they%20hold%20regular%20podcasts%20about%20Windows%20insider%20builds%20and%20I%20think%20they%20are%20also%20somehow%20connected%20to%20the%20Microsoft%20company%2C%20at%20least%20it%20feels%20like%20it%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-989006%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-989006%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3E%3CEM%3EI%20think%20people%20take%20articles%20from%20Windows%20central%20for%20granted%20because%20they%20hold%20regular%20podcasts%20about%20Windows%20insider%20builds%20...%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20think%2C%20and%20I%20think%20most%20people%20agree%2C%20that%20Windows%20Central%20is%20usually%20well-informed.%26nbsp%3B%20That%20doesn't%20change%20the%20fact%20that%20speculation%20is%20speculation%2C%20and%20attribution%20to%20sources%20is%20attribution%20to%20sources.%26nbsp%3B%20I%20take%20most%20of%20what%20I%20read%20in%20the%20trade%20press%20about%20Microsoft%20with%20a%20healthy%20skepticism%2C%20unless%20the%20information%20is%20tied%20to%20sources%20from%2Fwithin%20the%20company.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22%3CEM%3E...%20and%20I%20think%20they%20are%20also%20somehow%20connected%20to%20the%20Microsoft%20company%2C%20at%20least%20it%20feels%20like%20it.%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20don't%20think%20that%20Windows%20Central%20is%20connected%20to%20Microsoft**%20(other%20than%20to%20have%20developed%20sources%20within%20the%20company%2C%20as%20most%20reputable%20outlets%20in%20the%20trade%20press%20have%20done)%2C%20but%20if%20Windows%20Central%20is%20connected%20to%20Microsoft%20in%20any%20way%20beyond%20that%2C%20then%20Windows%20Central%20should%20disclose%20that%20fact%20in%20articles%20about%20Microsoft%20and%20Microsoft%20products%20published%20by%20Windows%20Central.%26nbsp%3B%20%3C%2FSPAN%3E%3CSPAN%3EReputable%20media%20disclose%20relationships%20with%20the%20companies%20that%20they%20report%20upon.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E**I%20did%20a%20quick%20look%20at%20relevant%20public%20records%2C%20and%20I%20cannot%20find%20any%20information%20suggesting%20that%20Windows%20Central%20is%20affiliated%20with%20Microsoft.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3EWindows%20Central%20is%20a%20media%20outlet%20of%20Mobile%20Nations%2C%20a%20division%20of%20Future%20Group%2C%20which%20owns%20%3CA%20href%3D%22https%3A%2F%2Fwww.futureplc.com%2Fbrands%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Enumerous%20media%20outlets%3C%2FA%3E.%26nbsp%3B%20I%20don't%20see%20any%20connection%20at%20all%20to%20Microsoft.%26nbsp%3B%20I%20believe%20Windows%20Central%20is%20reputable%2C%20independent%20outlet%20of%20the%20trade%20media%20reporting%20on%20Microsoft%20and%20its%20products.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-985250%22%20slang%3D%22en-US%22%3EEdge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985250%22%20slang%3D%22en-US%22%3E%3CP%3EApparently%2C%20we%20are%20not%20waiting%20until%202003%20(Update)%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fhappyface_40x40.gif%22%20alt%3D%22%3Ahappyface%3A%22%20title%3D%22%3Ahappyface%3A%22%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20395px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F155039iBEEDA59295348500%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22GA.jpg%22%20title%3D%22GA.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20from%20MS%2C%20btw%2C%20not%20an%20outside%20source.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-990146%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-990146%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EYes%2C%20Tom%20%26amp%3B%20the%20January%2015th%26nbsp%3B%3CU%3E%3CSTRONG%3Eexpected%3C%2FSTRONG%3E%3C%2FU%3E%20release%20date%20is%20from%20MS%20not%2C%20some%20outside%20source.%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2CDrew%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-990204%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-990204%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ETom%2C%20the%20(%3CU%3Eexpected%3C%2FU%3E)%20Jan%2C%2015th%20date%20is%20from%20MS%20not%20some%20outside%20source.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-990245%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-990245%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%3EThe%20article%20does%20not%20identify%20the%20source%20of%20the%20information%2C%20so%20it%20might%20or%20might%20not%20be%20accurate.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20does%2C%20in%20the%20first%20paragraph.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-990276%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-990276%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63137%22%20target%3D%22_blank%22%3E%40Bruce%20Roberts%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EBut%2C%20it%20is%20good%20to%20question%20everything%20one%20reads%20or%20is%20told%3B%20in%20case%20something%20is%2C%20actually%2C%20false.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-990362%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-990362%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63137%22%20target%3D%22_blank%22%3E%40Bruce%20Roberts%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3EIt%20does%2C%20in%20the%20first%20paragraph.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20first%20paragraph%2C%20which%20announces%20the%20January%2015%20release%20date%2C%20is%20clearly%20attributed.%26nbsp%3B%20Microsoft%20has%20confirmed%20that%20in%20other%20statements%2C%20as%20well.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20next%20two%20paragraphs%2C%20which%20were%20the%20subject%20of%20my%20comment%20and%20discuss%20how%20the%20the%20browser%20will%20be%20rolled%20out%20post-release%2C%20are%20not%20as%20clearly%20attributed%2C%20if%20attributed%20at%20all%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CEM%3EThe%20next%20question%20is%20that%20of%20when%20the%20browser%20will%20actually%20ship%20with%20Windows%2010%2C%20with%20many%20speculating%20that%20it%20might%20ship%20in%2020H1%20-%20which%20would%20be%20the%20first%20feature%20update%20after%20January%2015%20-%20or%20even%2020H2%2C%20since%2020H1%20might%20RTM%20in%20December.%20As%20it%20turns%20out%2C%20neither%20of%20those%20theories%20are%20accurate%2C%20as%20the%20browser%20will%20start%20to%20be%20bundled%20with%20the%20OS%20right%20after%20the%20GA%20date.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%22It's%20going%20to%20be%20a%20slow%20rollout%20though.%20We're%20not%20all%20going%20to%20wake%20up%20one%20day%20and%20find%20Legacy%20Edge%20replaced%20by%20the%20new%20Edge.%20That's%20how%20staged%20rollouts%20work%20though.%20There%20will%20be%20a%20small%20sample%20group%20that%20will%20get%20it%20first%2C%20and%20then%20that%20group%20will%20be%20expanded.%20As%20for%20new%20installations%20of%20Windows%2C%20the%20bits%20will%20be%20sent%20out%20to%20OEMs%20as%20soon%20as%20they're%20generally%20available.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20read%20the%20second%20and%20third%20paragraph%20as%20informed%20speculation.%26nbsp%3B%20I%20still%20do%2C%20in%20part%20because%20Microsoft%20has%20not%20confirmed%20the%20rollout%20process%20as%20far%20as%20I%20know%2C%20and%20other%20trade%20media%20have%20not%20picked%20up%20this%20thread%20in%20their%20reporting.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20trade%20press%20is%20widely%20reporting%20the%20January%2015%20release%20date%2C%20but%20I%20haven't%20seen%20other%20articles%20talking%20about%20the%20post-release%20rollout%20process.%26nbsp%3B%20That's%20odd%2C%20if%20Microsoft%20laid%20it%20out%20at%20Ignite%202019.%26nbsp%3B%20I%20would%20think%20that%20it%20would%20be%20big%20news%2C%20if%20Microsoft%20announced%20it%20at%20Ignite%202019%2C%20and%20other%20media%20don't%20seem%20to%20have%20picked%20that%20up.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20I%20can%20see%20that%20the%20alternative%20reading%20(that%20the%20Ignite%202019%20attribution%20applies%20to%20everything%20in%20the%20article)%20is%20also%20reasonable.%26nbsp%3B%20I%20can't%20dispute%20that%20your%20interpretation%20is%20reasonable%2C%20and%20I%20don't.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-991156%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-991156%22%20slang%3D%22en-US%22%3EYeah%20that%20they%20posted%20officially%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-991158%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20GA%20Release%20Date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-991158%22%20slang%3D%22en-US%22%3EIt's%20confirmed%20tho%20that%20Edge%20will%20be%20released%20without%20Extension%20sync%2C%20History%20sync%20and%20ARM64%20support.%3C%2FLINGO-BODY%3E
Drew1903
Trusted Contributor

Apparently, we are not waiting until 2003 (Update) :happyface:

GA.jpg

This is from MS, btw, not an outside source.

Cheers,
Drew

19 Replies
2003 is/was the probable Windows 10 build number for Edge insider to be intergrated into the OS, the release date of course was always different

@Drew1903 "Apparently, we are not waiting until 2003 (Update)"

 

Since it looks like 20H1 is going to RTM in December and since (as I understand it) 20H1 has not yet embedded Edge Chromium into the release, my guess is that Microsoft will embed Edge Chromium into Windows 10 as part of a monthly update sometime during 2020 or wait until 20H2.  Microsoft hasn't said anything about it yet, though, as far as I know, so your guess is as good as mine.

 

Version 79.0.309.nn is the release candidate for January 15, and when that has been released, then Microsoft will probably follow the Chromium development/release cycle, updating every six weeks or so going forward.  Microsoft has said that Edge Chromium updates will not be tied to the Windows 10 update cycle.

@tomscharbach 

Tom, some suggested & thought, including myself, that the GA for Edge C would, maybe, come with the Spring 2020 Update for Win10 (2003).  Seemed that might allow enough time to have the thing done; feels like there, still, is much to be done.  But, MS say it is expecting to release it mid-January.  So, that would, indeed, suggest Edge stuff is not tied to the 'every 6 months' major Updates of Win10.

Right now, Insider Builds have the same opportunity to run Edge (beta) Channels.  Once (new) Edge is embedded in the OS, it will be in the Insider Builds, too.  That's my 'guess', anyway.

It can be awkward trying to guess at things outside of Insider Builds by looking at what Insider Builds are doing; can be way out of sync with each other... especially when Fast Track & Skip Ahead split.

But, I'm sticking to the notion that once it's GA, we'll see it in the Insider Builds, too. Then it's, actually, truly, part of the OS.

Cheers,
Drew

I hope not..I'm on insider and I still enjoy Edge classic. the new Edge would just be useless for me since I use Canary and it has more features than stable build.

@Drew1903  I don't know how accurate this information is, but Neowin reported yesterday ("Microsoft's Edge Chromium browser to ship in Windows 10 as soon as it's 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."

 

@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 :lol: Que sera, sera.

Cheers,
Drew

Looks like it's their guess and they are not quoting any officials
The 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.

@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 ("Microsoft's Windows 10 20H1 release will be first to RTM in December under Azure schedule", 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.

@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.

I think people take articles from Windows central for granted because they hold regular podcasts about Windows insider builds and I think they are also somehow connected to the Microsoft company, at least it feels like it

@HotCakeX "I think people take articles from Windows central for granted because they hold regular podcasts about Windows insider builds ..."

 

I think, and I think most people agree, that Windows Central is usually well-informed.  That doesn't change the fact that speculation is speculation, and attribution to sources is attribution to sources.  I take most of what I read in the trade press about Microsoft with a healthy skepticism, unless the information is tied to sources from/within the company.

 

"... and I think they are also somehow connected to the Microsoft company, at least it feels like it."

 

I don't think that Windows Central is connected to Microsoft** (other than to have developed sources within the company, as most reputable outlets in the trade press have done), but if Windows Central is connected to Microsoft in any way beyond that, then Windows Central should disclose that fact in articles about Microsoft and Microsoft products published by Windows Central.  Reputable media disclose relationships with the companies that they report upon.

 

======================

 

**I did a quick look at relevant public records, and I cannot find any information suggesting that Windows Central is affiliated with Microsoft.  Windows Central is a media outlet of Mobile Nations, a division of Future Group, which owns numerous media outlets.  I don't see any connection at all to Microsoft.  I believe Windows Central is reputable, independent outlet of the trade media reporting on Microsoft and its products.

@tomscharbach 

Yes, Tom & the January 15th expected release date is from MS not, some outside source.  

Cheers,
Drew

@tomscharbach 

Tom, the (expected) Jan, 15th date is from MS not some outside source.

Cheers,
Drew

@tomscharbach 

"The article does not identify the source of the information, so it might or might not be accurate."

 

It does, in the first paragraph.

@Bruce Roberts 

But, it is good to question everything one reads or is told; in case something is, actually, false.

Cheers,
Drew

@Bruce Roberts "It does, in the first paragraph."

 

The first paragraph, which announces the January 15 release date, is clearly attributed.  Microsoft has confirmed that in other statements, as well.

 

The next two paragraphs, which were the subject of my comment and discuss how the the browser will be rolled out post-release, are not as clearly attributed, if attributed at all:

 

"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."

 

I read the second and third paragraph as informed speculation.  I still do, in part because Microsoft has not confirmed the rollout process as far as I know, and other trade media have not picked up this thread in their reporting. 

 

The trade press is widely reporting the January 15 release date, but I haven't seen other articles talking about the post-release rollout process.  That's odd, if Microsoft laid it out at Ignite 2019.  I would think that it would be big news, if Microsoft announced it at Ignite 2019, and other media don't seem to have picked that up.

 

However, I can see that the alternative reading (that the Ignite 2019 attribution applies to everything in the article) is also reasonable.  I can't dispute that your interpretation is reasonable, and I don't. 

Yeah that they posted officially
It's confirmed tho that Edge will be released without Extension sync, History sync and ARM64 support.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies