Jump to content

Mozilla Considers Slower Release Cycle For Firefox


Recommended Posts

Posted

Mozilla considers slower release cycle for Firefox

Esr-release-overview_610x344.png

Mozilla has proposed another system for releasing versions of the Firefox browser. Under the cycle, identified as the 'Extended Support Release', the cycle for unveiling new versions of the browser would become more suited to corporate environments. At present, new versions of Firefox (standard builds) are released every six weeks, and now they are suggesting change again, as CNET reports.

In June, the company experienced backlash from different businesses due to the nature of the release cycle. The company responded by working on a compromise, through a group known as the 'Enterprise Working Group'. The result of the group's work has been this proposal. With ESR, Mozilla wants to capture the developing markets of both home users and slower-moving users. In a corporate environment, software is generally tested before being pushed to all workstations on the network, and therefore, the current system used for Firefox presents issues. It has to be constantly tested for updates, and therefore, Mozilla does not want to lose the business sector of the market.

Mozilla are aware that they cannot afford to release builds too slowly, but they can also no longer release them at an extreme pace without some form of compromise. If they move too slowly, Google is in a prime position to push Chrome as an alternative. If they move too slowly, users could easily be swayed back to Microsoft's Internet Explorer, with the promise that the browser is becoming more modernized.

And yet, despite the backlash from businesses, some minds at Mozilla have suggested the possibility of an even faster release cycle. It seems likely that the browser updates will become 'silent', much like Google Chrome. The idea behind an even faster, silent cycle stems from the anger and confusion over version numbers. With a silent cycle, developers could immediately add new functionality instead of delaying it until the release date, which could be anywhere up to six weeks after.

On September 21st, Mozilla's Kev Needham made an official post about the changes, as well as the ESR. An excerpt of his post, justifying the reasoning for another cycle is below, while the post can be read in its entirety here.

Since moving to a faster release process, Mozilla understands that some organizations are facing challenges in deploying Mozilla products in a managed environment.

Mozilla has already attracted some heat for changing the manner in which it deploys updates, though this controversy seems to have grown less frequently discussed as more users grow accustomed to the new releases.

Source: Neowin.net

Posted

This doesn't seem to address the problem with add-on/extension support as the version numbers change radically between the Enterprise releases. Add-ons/extensions are what brings about the usefulness of Firefox over other browsers.

Seems to me to be more shallow reasoning.

Posted

No one cares how it works - just make it work, Mozilla.

It should work the same as Chrome, which somehow manages to update silently, without showing grand dialogues or needing to restart the browser.

What Firefox does now is the worst UI imaginable: At a time when I most definitely want to do something else - e.g. I just fired up the browser, so quite likely there was a reason for that, I wanted to do something - it's interrupting me with news about updates, a restart, and a report on incompatible extensions. This is really dumb.

Maybe show me a little info bar that says I have disabled extensions if my extensions can't be upgraded. Other than that, do not bother me. Chrome can do it...

Posted

I personally prefer programs that give you the choice to upgrade or not rather than doing it in the background without your consent.

Posted

It should work the same as Chrome, which somehow manages to update silently, without showing grand dialogues or needing to restart the browser.

The update restart requirement applies to Chrome as well.

Posted

Iv been using Firefox for a while and because of a problem with firefox( open new windows in a new tab becomes unticked) i tried Chrome, there is a lot of hype about Chrome but they have nowhere near the same extensions as Firefox, and now with FF7 it seems to be faster so Im going back with them, when chrome allow you to do simple things like remove the 'other boomarks link'; while still keeping bookmarks or allow you to tag bookmarks then maybe i will reconsider, i would like to see tabs in seperate instances in FF but thats a small thing

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.



×
×
  • Create New...