Stable to 80.0.361.48 yesterday same as Beta: a bit early??

%3CLINGO-SUB%20id%3D%22lingo-sub-1164183%22%20slang%3D%22en-US%22%3EStable%20to%2080.0.361.48%20yesterday%20same%20as%20Beta%3A%20a%20bit%20early%3F%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1164183%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20reader%2C%3C%2FP%3E%3CP%3EThis%20morning%20I%20found%20out%20that%20stable%20went%20from%2079%20to%2080%20yesterday%2C%20which%20I%20found%20a%20bit%20early%2C%20expecting%20it%20to%20go%20to%2080%20on%20the%2026th%20of%20February%20(15%20januari%20relaease%20%2B%206%20weeks).%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20off%3F%3F%3C%2FP%3E%3CP%3EEven%20more%20surprised%20to%20find%20Beta%20still%20at%20the%20same%20version...%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Ffacepalm_40x40.gif%22%20alt%3D%22%3Afacepalm%3A%22%20title%3D%22%3Afacepalm%3A%22%20%2F%3E%3C%2FP%3E%3CP%3EI%20probably%20missed%20something%2C%20right%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%20Henno.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1164228%22%20slang%3D%22en-US%22%3ERe%3A%20Stable%20to%2080.0.361.48%20yesterday%20same%20as%20Beta%3A%20a%20bit%20early%3F%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1164228%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3Eeverything%20is%20normal.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20first%20you%20need%20to%20read%20this%20article%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fmicrosoft-advisory-shows-whether-edge-keeps-up-with-chrome-s%2Ftd-p%2F1157798%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fmicrosoft-advisory-shows-whether-edge-keeps-up-with-chrome-s%2Ftd-p%2F1157798%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHere%20is%20the%20Changelog%20for%20Edge%20stable%2080%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-au%2Fdeployedge%2Fmicrosoft-edge-relnote-stable-channel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-au%2Fdeployedge%2Fmicrosoft-edge-relnote-stable-channel%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EChrome%20is%20version%2080%2C%20after%203%20days%2C%20Microsoft%20released%20Edge%20version%2080%20too.%20they%20HAD%20to%2C%20because%20each%20update%20fixes%20serious%20security%20vulnerabilities.%3CBR%20%2F%3Eand%20it%20was%20most%20likely%20the%20first%20and%20last%20time%20Microsoft%20did%20it%2C%20only%20to%20align%20themselves%20with%20Chromium%20release%20cycle%20and%20stay%20up-to-date%20with%20the%20security%20patches%20inside%20Chromium%20builds.%20going%20forward%2C%20Microsoft%20will%20stick%20to%20their%20correct%20release%20schedule%20which%20is%20every%206%20weeks%2C%20just%20like%20Chrome.%3CBR%20%2F%3E%3CBR%20%2F%3Ecurrently%2C%20there%20is%20a%203%20days%20gap%2C%20so%20after%20Chrome%2080%20was%20released%2C%20Microsoft%20released%20Edge%2080%203%20days%20later.%20I%20hope%20next%20time%20it%20won't%20be%20that%20much%20and%20comes%20down%20to%201%20day.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1164236%22%20slang%3D%22en-US%22%3ERe%3A%20Stable%20to%2080.0.361.48%20yesterday%20same%20as%20Beta%3A%20a%20bit%20early%3F%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1164236%22%20slang%3D%22en-US%22%3EAbout%20the%20beta%20channel%2C%20it%20usually%20lags%20behind%20the%20schedule.%20when%20I%20had%20been%20on%20Chrome%20beta%20channel%2C%20I%20had%20to%20wait%20few%20days%20before%20I%20could%20get%20the%20next%20major%20build.%3CBR%20%2F%3EI%20assume%20the%20for%20Edge%20it's%20the%20same.%20once%20Edge%20Dev%20moves%20over%20to%2082%2C%20Beta%20channel%20will%20receive%20its%20first%2081%20build%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Dear reader,

This morning I found out that stable went from 79 to 80 yesterday, which I found a bit early, expecting it to go to 80 on the 26th of February (15 januari relaease + 6 weeks). 

Am I off??

Even more surprised to find Beta still at the same version... :facepalm:

I probably missed something, right?

 

Regards, Henno.

2 Replies
Highlighted
Hi,
everything is normal.

I think first you need to read this article:
https://techcommunity.microsoft.com/t5/discussions/microsoft-advisory-shows-whether-edge-keeps-up-wi...

Here is the Changelog for Edge stable 80:
https://docs.microsoft.com/en-au/deployedge/microsoft-edge-relnote-stable-channel

Chrome is version 80, after 3 days, Microsoft released Edge version 80 too. they HAD to, because each update fixes serious security vulnerabilities.
and it was most likely the first and last time Microsoft did it, only to align themselves with Chromium release cycle and stay up-to-date with the security patches inside Chromium builds. going forward, Microsoft will stick to their correct release schedule which is every 6 weeks, just like Chrome.

currently, there is a 3 days gap, so after Chrome 80 was released, Microsoft released Edge 80 3 days later. I hope next time it won't be that much and comes down to 1 day.

Highlighted
About the beta channel, it usually lags behind the schedule. when I had been on Chrome beta channel, I had to wait few days before I could get the next major build.
I assume the for Edge it's the same. once Edge Dev moves over to 82, Beta channel will receive its first 81 build :)