Mozilla Firefox 5 , 6 beta Versions
Recently Mozilla release there next generations Web browser's, Firefox 5 and 6.
Mozilla Firefox 5 is called Aurora and Firefox 6 is called Nightly .
New Firefox 5 and 6 look like Firefox 4..I can't find any other changes.But Mozilla introduce some new features to these software.Microsoft also announce there Internet Explore 10.Now we can download preview versions.Due to these movements every other browser's like Opera ,Safari,Chrome will release there new versions.
After Chrome browser,Firefox demand decrease,Some Firefox users turns towards Chrome browsers.Firefox introduce these two updates to overcome Chromes Effects.
Firefox 5 and 6 .
Firefox 5 and 6 support HTML 5 and more,It take only less hardware.The Main Problem of Firefox is "High Hardware Usage". This become problem when we use a small minimum computer's.Now it take only less hardware.They also increase Firefox start up time.More Browsing speed,10x compared with older versions.They use new icon set for both 5 and 6.Take a look on Firefox 6 icon.
Download Firefox 5 Aurora
Download:Firefox 5 Aurora
Download Firefox 6 Nightly
Download:Firefox Nightly
Download Mozilla Firefox 8 for 64 bit Processors
Download Mozilla Firefox 8 for 32 bit Processors
From Mozilla blogs:
"With the new structure,
1. The quality expectation for updates on the Beta channel is vastly higher than the updates on the Nightly channel.
We address this by creating the Aurora channel. This channel has higher expectations of quality than the Nightly channel but lower expectations than Beta. At the start of the 6 week1 Aurora period for a particular release, the quality will be closer to the Nightly channel. At the end of the 6 week Aurora period quality will have converged to match the Beta channel.
2. Users on the Beta channel may not even know they are running pre-release (but hopefully decent) versions of Firefox.To fix this issue we are branding builds from individual channels with new icons.
This should allow users to know at a glance what channel they are on and set stability expectations accordingly.
Due to #1 above, development on the mozilla-central repository is frozen while we stabilize for an update to the Beta channel. This causes a huge backlog of patches and adds additional risk for the next beta.
Because we are using a repo-per-channel model, mozilla-central development (and thus the updates on the Nightly channel) never have to freeze…quality convergence takes place on other repositories while Firefox development continues on mozilla-central unaffected by the release process.
3. 3rd parties must track Firefox development closely to know when a milestone they care about (such as feature complete, API freeze, or string freeze) is reached.
With the new process what happens where and when is a lot more explicit and consistent. No longer will 3rd parties need to know that beta 8 was API complete while beta 9 was string frozen. Instead we can make assurances such as “no new en-US strings will be added through updates on the Aurora channel” and “no extension API changes will be delivered to users via the Beta channel”. This allows 3rd parties to accurately plan and encourages sticking to the rules and schedule
4.. For developers, the tree rules are constantly changing on mozilla-central depending on when we last shipped an update from it.
Lastly, the new repositories (which map to the channels) allow developers to do what they do best—develop. No longer should a developer need to know we are in blocker-only mode for a particular release. Instead, they will be allowed to land their fixes on mozilla-central at any time provided they stick to the mozilla-central tree rules.
The mozilla-aurora repository will have different rules, and mozilla-beta will have different (and stricter) rules still. The rules for each of these repositories will not change over time or from release to release, which should help alleviate a lot of developer confusion and annoyance"
Labels: Internet Funs, Softwares