You should now be used to its fast release pace, so it’s probably not a surprise. Chromium 12 has just been released upstream less than 2 hours ago, 6 weeks after Chromium 11. Thanks to a good preparation with the Daily PPA and Dev and Beta Channels, I’ve been able to quickly ship this major Stable release to Ubuntu. While it’s making its way to the repositories, you can as usual grab it from the stable channel for Lucid, Maverick, Natty and Oneiric. Note that those using the beta channel received the same version a few hours ago.
Chromium 12 comes with a lot of new great features, including hardware accelerated 3D CSS and a new safe browsing protection system. Note that if you were using the Google Gears plugin, it’s no longer supported. For that, the HTML5 offline feature is preferred. This release also fixes more than a dozen of security issues.
If you use Unity, the Chromium Quicklist has been translated in 21 languages since the last update around 2 weeks ago.
Following the official announcements of End of Life of Hardy Desktop (8.04) and Karmic (9.10) , and as previously mentioned in this blog, I just dropped support for those two distributions in the 4 Chromium channels/PPAs.
I could have decided to continue maintaining Chromium there, but with everything else unmaintained, it’s not wise to continue to pretend supporting a browser, which is the most exposed part of a desktop. To make the matter clear, I also dropped the binaries. Read more…
Just committed this to my main Chromium packaging branch, it will be in the next daily tomorrow.
..it will need translations.
Chromium (trunk) recently improved its integration into Unity.
Some already noticed the download progress bar in the Unity launcher (the chromium icon in the side panel). But there’s more.
If you have “Experimental GNOME menu bar support” enabled in about:flags, you’ve probably noticed the global menu a few weeks ago. Read more…
As the Chromium maintainer for Ubuntu, I often wonder how many users installed the different packages I maintain. It’s obviously difficult, not to say impossible, to tell how many of those are active users, mostly because it would imply adding some ping back mechanism that would hurt the privacy of some of those users, a line I am not willing to cross. So to try to answer this question, I depend on publicly available data.
To start with, I need to see where users are taking their chromium packages from. Read more…