Ubuntu 14.10 "Utopic Unicorn" Arrives in a Few Days
When Ubuntu hits the Final Freeze point the developers stop pushing updates and changes, and everyone focuses on the major bugs and problems that haven't been fixed yet. An exception can be made if something really terrible happens, but that wasn't the case until now and it's unlikely to occur.
Now, Ubuntu 14.10 (Utopic Unicorn) is scheduled to arrive on October 23, this Thursday. Users will be offered the chance to upgrade their systems, but this is an intermediary release and it's not likely that many users will take this step. The Ubuntu LTS release was just six months ago and not too many users are going to exchange the five years of support for 14.04 with just nine months for 14.10.
Meizu MX4 Pro Spotter Running Ubuntu Touch
For now, we don’t know which device will be running Ubuntu Touch, but due to the fact that Meizu MX4 Pro has been postponed to November, it may be it. The MX4 Pro uses a 5.4 inch display with 1536 x 2560 resilution, a 20 MPX rear camera + a 13 MPX front camera, a Samsung octa-core Exynos 5430 CPU and 3 GB of RAM.
KDE Telepathy 0.9.0 Released
Today we released the 0.9 series of KDE Telepathy, a multiprotocol instant messaging client for Plasma.
Amongst the many bugfixes the following features are worth highlighting.
Porteus 3.1 RC1 Is a Bleeding Edge Slackaware-Based Distro with Linux Kernel 3.17
Porteus is a special operating system that is designed to be very fast and feature all kind of bleeding edge features. It's also optimized to run from all sorts of mediums, not just hard disks. It's built on Slackware and it's extremely small, a characteristic that is determined by the fact that it's always loaded completely in the memory.
Another interesting aspect of the distro is the fact that it uses modules instead of a package manager. These modules can precompiled for the operating system and users can just activate and deactivate them. Also, installing modules in Porteus works very intuitively and it can be done by double clicking on the modules.
oVirt 3.5 Rolls Out
This past week was the KVM Forum, a three-day event in Düsseldorf that brought together the entire KVM community, which included oVirt users and developers. The October 16th oVirt Workshop, a free-of-charge event co-located with the KVM Forum, focused on the oVirt datacenter platform and its use in business and academic worlds.
So when I released 3.17, I said that I'd extend the merge window to
three weeks due to travel.
I clearly lied.
Because here we are, the usual two weeks later, and I've already
pushed out 3.18-rc1.
What happened is that not only did I merge actively despite travels -
I was out of communication just for a couple of days (almost, but not
entirely, due to flights - the hotel in DÃsseldorf lost all internet
for a day too). But perhaps more importantly, people seem to have
aggressively sent in their pull requests, because rc1 contains more
than linux-next did a couple of days after 3.17.. So holding it up
another week just seems pointless.
That said, I realize that people might have taken my statements at
face value, and planned with that in mind. I hate it when I get pull
requests really late in the merge window, but having closed it as per
the regular schedule, I also understand that somebody might have
planned on sending their pull request a bit later. It's ok. Grovel a
bit, and explain what's up, and you can almost certainly guilt me into
Also, maybe I just missed something due to jetlag (hmm. yes, let's
call it "jetlag", that sounds so much better than "core incompetence
and bad planning"), so if you feel unfairly overlooked, send me a note
explaining how I've unfairly wronged you.
There is also at least one pull request that I am hoping to get asap
and planning on still pulling, ie I'm very much still hoping to get
overlayfs finally merged. But there were a few last-minute questions
from Al. Assuming that all works out, that's an expected late pull.
Not worth holding up the rc1 release for one known straggler, though.
So there you have it. The merge window is closed, but with room for
excuses and possible missed requests. As usual, the shortlog is much
too big to post (core stats: roughly 74% drivers, 10% architecture
updates, the rest networking, filesystems, core kernel, documentation,
include files, tool updates...), and the appended is my "mergelog"
which as usual credits the people I pulled from, which is not at all
necessarily the same as the people writing the code.
Go forth and test,
Firefox Hello Not Working and Mozilla Claims the Bug is Invalid
Mozilla announced the Firefox 34 Beta release on October 17 and a key highlight is the new Firefox Hello feature. Firefox Hello is supposed to enable users to simply use the browser to be able to call each other.