![]() ![]() Be able to control feature rollout based on release readiness.Speed up the regression feedback loop from rollout to detection to resolution.Ensure Firefox engineering productivity is not negatively impacted.In order to maintain quality and minimize risk in a shortened cycle, we must: (This is what we’ve been doing recently with CSS spec implementations and updates, for instance.) Also, we put new features and implementation of new Web APIs into the hands of developers more quickly. With four-week cycles, we can be more agile and ship features faster, while applying the same rigor and due diligence needed for a high-quality and stable release. Shorter release cycles provide greater flexibility to support product planning and priority changes due to business or market requirements. The next two major ESR releases will be ~June 2020 and ~June 2021. In the years to come, we anticipate a major ESR release every 12 months with 3 months support overlap between new ESR and end-of-life of previous ESR. Firefox ESR release cadence ( Extended Support Release for the enterprise) will remain the same. Starting Q1 2020, we plan to ship a major Firefox release every 4 weeks. Considering these factors, it is time we changed our release cadence. Feature teams are increasingly working in sprints that align better with shorter release cycles. In recent quarters, we’ve had many requests to take features to market sooner. Today’s announcementĪnd today we’re excited to announce that we’re moving to a four-week release cycle! We’re adjusting our cadence to increase our agility, and bring you new features more quickly. With this approach, we can test and stabilize new features before delivering them to the majority of Firefox users via general release. To optimize the process, and make it more reliable for all users, over the years we’ve developed a phased release strategy that includes ‘pre-release’ channels: Firefox Nightly, Beta, and Developer Edition. Building and releasing a browser is complicated and involves many players. We typically ship a major Firefox browser (Desktop and Android) release every 6 to 8 weeks. We’ve updated this post with the following correction: The SeaMonkey Project consumes Firefox releases, not SpiderMonkey, which is Firefox’s JavaScript engine. ![]() Needham, however, said that the details of the plan were "to be determined," perhaps leaving open an option that would make it difficult, if not impossible, for individuals to grab the ESR editions.Editor’s Note: Wednesday, 10:40am PT. "The ESR is targeted specifically at organizations who face the challenges it addresses, not individual users." "We want to ensure it will be an explicit choice to select the ESR and we won't recommend it for individual use," said Kev Needham, Mozilla's channel manager, in an email reply to questions. But Mozilla will, at the least, discourage others from adopting the slower release schedule. There was nothing in Mozilla's proposal that indicated a technical barrier to non-business users climbing on the ESR train. "It's simply because Firefox works 'good enough' right now and they don't want to have to deal with change." "The reason I expect a lot of users to switch to these ESR builds is not because they want extensions to work or because of any one issue that we can fix in the future," said Cheng Wang on the discussion group last week. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |