Install The Newest Firefox ppa with command "add-apt-repository" (9.10 & above)

[SilverWave]

firefox - 6.0~b2+build1+nobinonly-0ubuntu0.11.04.1~mfn1

[SilverWave]

firefox-trunk - 8.0~a1~hg20110714r72818+nobinonly-0ubuntu1~umd1~natty

All look OK except the i386 Oneiric build.

[SilverWave]

firefox - 6.0~b2+build1+nobinonly-0ubuntu0.11.04.1~mfn1

Just updated with the latest Beta refresh aka b2

[SilverWave]

Every Six Weeks

[lovinglinux]

Electrolysis project coming back:

http://arstechnica.com/open-source/n...ementation.ars

http://blog.mozilla.com/products/201...ocess-firefox/

http://www.conceivablytech.com/8478/...-to-run-faster

[SilverWave]

Electrolysis project coming back:

http://arstechnica.com/open-source/n...ementation.ars

http://blog.mozilla.com/products/201...ocess-firefox/

http://www.conceivablytech.com/8478/...-to-run-faster

Interesting but I don’t think I will be holding my breath while we wait

[lovinglinux]

Interesting but I don’t think I will be holding my breath while we wait

It will certainly take a lot of time to land on our hands.

[lovinglinux]

Good news about Panorama feature.

http://www.conceivablytech.com/8520/...refox-panorama

The new improvements are already available in Firefox 6, 7 and 8.

I am becoming a big fan of the fast release cycle

[SilverWave]

Well natty 64bit is done and working fine ATM, but the rest may take a little longer show up in the PPA's

Changes for the versions:
8.0~a1~hg20110714r72818+nobinonly-0ubuntu1~umd1~natty
8.0~a1~hg20110721r73087+nobinonly-0ubuntu1~umd1~natty

This change is not from a source that supports changelogs.

[lovinglinux]

Automated daily builds now only occur if there are changes

Previously, early in the morning the build system blindly updated to the latest tip of tree, built it, generated updates, and made them available on the proper channel–even if there were no changes since the last time. This was inefficient for users, a poor use of build system resources, and unnecessarily contributed to update fatigue for less-active channels.

The new behavior makes it so automated morning builds only occur when the code or dependent localizations have actually changed since the last update.