Mozilla Kills Firefox Aurora Channel, Builds Will Move Directly From Nightly To Beta (venturebeat.com)

Mozilla said today it is killing the Firefox Aurora channel, six years after it was first introduced in April 2011. The move comes as, Aurora failed to live up to the company's expectations as a "first stabilization channel." Moving forward, the absence of Aurora will help the company streamline its browser's release process and bring stable new features to users and developers faster. From a report: The Firefox Aurora channel sat between the Nightly and Beta channels. Until now, Firefox development started with Nightly, which consists of the latest Firefox code packaged up every night for bleeding-edge testers, and was then followed by Aurora, which includes everything that is labeled as "experimental," then Beta, and then finally the release channel for the broader public. Going forward, builds will move from Nightly to Beta to Release. The Firefox Developer Edition, which the company calls "the first browser created specifically for developers," will be based on the Beta channel instead of Aurora. Developer Edition users should keep their existing profile, themes, tools, preferences, and "should not experience any disruption," Mozilla promises.

Comments

I don't use chrome, am curious why you switched

[Ungrounded Lightning]

Using Firefox in Linux is truly painful anymore, I quickly use it to install Chrome these days.

I don't use chrome, and am curious why you do.

1) When an employer's IT guy deployed it as the default browser, a few years back, I stopped using it (and installed Firefox) when a typo brought up a NSFW site - and then I couldn't get Chrome to dump it from the autocomplete (even by following their excuse for online documentation), where it insisted it be the top entry whenever I typed the first keystroke of a site name that started with the same first letter.

2) Like several appliances, its voice-typing feature forwards the sound samples over the Internet to servers - acting as a room bug. (Even if it doesn't do this all the time - and how do you know it doesn't? - it provides the infrastructure for trivial malware hacks to do so.)

3) The version on my new Android smartphone has a click-through license that includes an adobe license, which in turn constrains the user - for the rest of his life - to not compete with Adobe's products or work on security matters related to them. Accepting that (on an appliance that is identifiable as mine and no doubt "phones home" with the acceptance) would be a career limiting move.

So I don't use Chrome, and don't understand why any computer professional would.