christianlosa.blogg.se

Microsoft edge browser chrome release cycle
Microsoft edge browser chrome release cycle









During the first four weeks of this milestone, both stable and extended stable are shipped identical releases see the channel lifecycle to learn more. Extended StableĬhrome Browser also maintains every other milestone branch for four additional weeks by backporting important security fixes to create an extended stable channel, where a new milestone is shipped every eight weeks. Once a milestone reaches stable, biweekly updates (called refreshes) are shipped to the stable to deploy security fixes and keep Chrome’s patch gap short. The new milestone is developed on main for four weeks (beginning on branch point for the previous milestone) before the milestone‘s branch is cut, which is then stabilized for six weeks before being shipped to stable. Chrome ships a new milestone (major version) to the stable channel every four weeks.











Microsoft edge browser chrome release cycle