OStatic

It's one of the biggest gotchas for alternative operating systems -- at some point in the middle of one project's release cycle, some other component that's tied in some way to the original project's functionality gets a whizbang new update that's significant enough that full-fledged integration has to wait until the next release. Of course, there are ways around this for those who just can't wait, but these work arounds might not always be as straightforward as one would hope.

The KDE team continues to roll out updates, enhancements and new features for the KDE 4 desktop environment. The sticking point here is that different users on different machines might find the updates are neat little improvements -- or absolutely vital. And a distribution needs to balance stability and utility of its official packages with the needs of its userbase.

The openSUSE community recently took charge of this particular situation in the form of the openSUSE 11.1 KDE4 Reloaded respin. The installable liveCD, masterminded by Stephan 'Beineri' Binner, incorporates the openSUSE 11.1 image (complete with updates issued since its release) and the KDE 4.2.2 desktop.

Late yesterday afternoon, Canonical let loose the release candidate disk images for Ubuntu 9.04 (Jaunty Jackalope). Canonical warns that while a release candidate is about as stable as one can get with a testing release, it is still a testing release, and users should hold off installing Jaunty on essential systems.

The good news, of course, is that those clamoring to install Jaunty on their essential systems haven't long to wait. The finalized, stable Jaunty release will appear on mirrors worldwide April 23rd.

Late last week, Sam took a close look at the rapidly changing browser landscape. In one of the posts linked therein, Keir Thomas speculates that Firefox may well have just given up the ghost, what with an alpha version of Chrome now being available for Linux (or, at the very least, Ubuntu).

I don't think it is, nor is it going to be, quite that easy. Firefox isn't without issue -- or momentum. And Chrome for Linux? In all reality, it doesn't exist, yet. Chrome may have a number of advantages over other browsers, including Firefox, on other platforms. But if it's still too early to call this fight on Windows, declaring the superior browser on Linux is pretty much a coin toss.

When Google's Marissa Mayer told TechCrunch's Michael Arrington that Chrome would drop the beta designation less than two days ago, the implication was that it would happen pretty quickly. When you consider the length of some beta stages (and drawn out, fanfare driven gold releases), Chrome's 1.0 release yesterday was fast and relatively quiet.

InformationWeek shares a little of my aforementioned concern that taking an application out of the testing stage prematurely can have some serious consequences, and it does offer some insight into Google's thought processes.

On Monday, the Mozilla team announced the general availability of Firefox 3.1 beta 2 for testing. Aside from increased localization support, a new Private Browsing mode, new tab switching and preview behaviors, and support for a number of new web technologies (such as the W3C Geolocation API and offline applications), the new beta release uses the TraceMonkey JavaScript engine by default, and has made tweaks to the Gecko engine to speed content rendering.

Today, both Ubuntu and openSUSE are releasing beta versions of their upcoming releases.

Ubuntu's 8.10 is in its first beta version, and openSUSE 11.1 plans on issuing its second beta release shortly.

The openSUSE Project recently announced the availability of openSUSE 11.1 Beta 1 for wide scale testing and bug squashing. This development release is available in x86, x86-64 and PPC architectures as a DVD disk image (liveCDs are not available for the current beta).

The 11.1 beta provides a decently solid look at where the final release is heading. As with any development release, there are known bugs that vary in severity and new or updated features that the development team is encouraging users try out, in order to find and resolve any bugs and suggest changes and improvements.

Red Hat, along with the City University of New York and Intel, announced yesterday that they are creating the New York City Open Source Solutions Lab. This lab, which will be headquartered at CUNY's Institute for Software Design and Development in Manhattan, is aimed at helping local and state government agencies in New York take advantage of open-source solutions. The lab will provide governments with the ability to develop and test a variety of open-source technologies running on Intel chips.

PHP is not the sexiest language, and many people are quick to point out its deficiencies for Web application development. However, PHP is one of the most popular open-source projects, with a huge following, and many installations. Given that it is a relatively stable project, you might expect the PHP development team to be resting on its laurels. But no; in addition to a regular bug-fix release, the PHP QA team is sponsoring a test fest, in an attempt to improve the language's automated test suite.