So, say a feature lands in Nightly on August 6 (one day before merge) that feature would then ship in Firefox on September 26. Wow this took long enough :) this was being discussed as an idea years ago April 17th, 2017 at 10:08 The theme, some options are enabled in devedition and not beta, different profile, etc April 25th, 2017 at 05:14 Which differences will be between Beta and Developer Edition? April 17th, 2017 at 09:29 Sign up for the Mozilla Developer Newsletter: articles by Sylvestre Ledru… Discover great resources for web development.She's passionate about keeping the web open and working on things developers love (like MDN).ĭave Camp is Director of Engineering for Firefox at Mozilla. AboutĪli Ali is the head of Developer Ecosystem at Mozilla, and has been developing and managing web sites for longer than she cares to admit. Monitoring crash rates, QE’s sign offs, telemetry data and new regressions to determine overall Nightly quality and feature readiness to merge to Beta.įor a deeper dive into transition details, please see the Mozilla Release Management blog for in-depth answers to the most common questions about this change.The ability to identify potential risks carried by changes before they even land by correlating various data sources (VCS, Bugzilla, etc.) in order to identify functions where a modification is more likely to induce a regression.
#Mozilla firefox version 54 download code#
Code coverage results will be used to analyze the quality of the test-suite and the risk introduced by the change.They will be able to identify potential defects while minimizing technical debt. Static analyzers integrated as part of the workflow, in order to detect issues during the review phase.If features are not ready, they won’t migrate from Nightly to Beta. A new feature will merge from Nightly to Beta only when it’s deemed ready, based on preestablished criteria determined by our engineering, product and product integrity teams. Our engineering and release workflow will continue to have additional checks and balances rolled out to ensure we ship a high quality release. Today, in 2017, we have more modern processes underlying our train model, and believe we can deliver feature-rich, stable products without the additional 6-8 week Aurora phase.Ī staged rollout mechanism, similar to what we do today with Release, will be used for the first weeks of Beta. On Android, Aurora users will be migrated to Nightly.Īurora was originally created in 2011 to provide more user feedback after Firefox shifted from version 5 to the high-speed release cycle.
#Mozilla firefox version 54 download update#
Between April and June, Firefox Aurora on Desktop (54) will continue to receive updates for critical security issues and the Aurora and Developer Edition populations will be migrated to the Beta update channel. On the next merge day, June 12, Firefox 55 will move directly from Nightly to Beta. Here’s the timeline: On April 18, code for Firefox 54 will move from Aurora to Beta as usual, while Firefox 55 will remain on Nightly for a second cycle in a row (a total of 14 weeks).