Mozilla Introduces Aurora, The Pre-Beta, Post-Nightly Firefox(techcrunch.com)
techcrunch.com
Mozilla Introduces Aurora, The Pre-Beta, Post-Nightly Firefox
http://techcrunch.com/2011/04/13/mozilla-aurora/
7 comments
"This was generally rejected due to alpha having existing connotations. Aurora could be crashier than an alpha. Also, it is better to talk about Aurora as a separate entity rather than an alpha of Firefox (which is why the branding is different)." http://groups.google.com/group/mozilla.dev.planning/msg/8105...
> Aurora could be crashier than an alpha.
I think "beta" (even a "pre-beta") connotes more stability than "alpha". Pre-beta sounds like a "beta rc1".
I think "beta" (even a "pre-beta") connotes more stability than "alpha". Pre-beta sounds like a "beta rc1".
Okay, so there's no problem. Aurora isn't the name for a crashier-than-alpha beta. Beta is still beta, and it is more stable than aurora (the alpha).
Can't wait to see how stable this is. The Chrome dev channel has been surprisingly stable for me (usable for day-to-day browsing).
Actually minefield (now called nightly) is usually stable enough, it's rare that there is a serious problem. So Aurora will probably be ok in stability.
What about extension compatibility?
Extensions will be automatically marked compatible with the new release, unless there are known problems: http://blog.mozilla.com/addons/2011/04/13/add-ons-review-upd...
Those icons are actually pretty slick.
This is one area where I've long admired Firefox... and it's benefitted them for mainstream market-share penetration.
When they release something to even beta, it looks very interesting and exciting.
When they release something to even beta, it looks very interesting and exciting.
Agreed. The "Minefield" (besides being a terrible alpha/pre-release codename) icon left a lot to be desired.
Mozilla nightly builds have always (AFAIK) been called Minefield. The name discourages non-developers from installing it (unless they mistake Minefield for a new version of Minesweep). :)
Here's a link to the Firefox Channels page, if you want to check out Aurora. It's rather hard to navigate to from the techcrunch article.
http://www.mozilla.com/en-US/firefox/channel/
http://www.mozilla.com/en-US/firefox/channel/
I don't know who named this but they had to be really removed from the browser world to not know about Arora. http://code.google.com/p/arora/
Maybe the same people who named a JS minifier "Closure" and a web browser "Chrome".
I give the Mozilla guys kudos for realizing they were starting to fall into the same malaise that the IE team had slumped into and are actively working to get back to a faster, more iterative development model.
Maybe you experienced a different history of the last decade than I did, but in my history the IE team completely disappeared from 2001 until 2007. Suggesting that the Firefox team has ever been anything like is just silly.
Yes, a year between major releases is kind of a long time today, but it's not the better part of a decade and it's not "disappearing" either.
Given the choice between 1 release per year with (hypothetically) 12 new features or 3 releases per year with 4 new features each, clearly the faster releases are better for the Web and for users. But delivering 12 new features a year in one lump rather than in three lumps is not a "slump" and can not rightly be called "malaise" either.
The "pace" of development has never been slow at Mozilla, only the pace of "releases" and that's what we're fixing here.
Yes, a year between major releases is kind of a long time today, but it's not the better part of a decade and it's not "disappearing" either.
Given the choice between 1 release per year with (hypothetically) 12 new features or 3 releases per year with 4 new features each, clearly the faster releases are better for the Web and for users. But delivering 12 new features a year in one lump rather than in three lumps is not a "slump" and can not rightly be called "malaise" either.
The "pace" of development has never been slow at Mozilla, only the pace of "releases" and that's what we're fixing here.
Well, I said they started to. You're right, the Mozilla guys never stopped developing but with Chrome coming out and seemingly running circles around them I definitely felt like they were going the way of the dinosaur. I will readily admit it was more perception than reality.
Congrats to the Mozilla team though for their ramp up in production speed. Nice to see.