Churning out an x.0 software release must be akin to becoming a new parent -- the event exudes promise, joy, and hope, yet is simultaneously humbling, exhausting, and terror-inducing. While it isn't realistically possible to plan out detailed roadmaps for your children's long-term future, it's crucial to do so for a software project. While whether the presence of a carefully planned roadmap makes progress more or less stressful depends largely on who you ask and at what point you're asking, a project with clearly outlined goals and direction has a much better shot at sustained developer interest and solid releases.

Many projects grapple with this, and as GNOME pushes towards its 3.0 milestone, the GNOME Release Team talks about the voyage to this point -- and how best to travel forward from where it currently stands.

Xfce is one of the hidden gems of the free desktop. It has managed -- quite successfully -- to capture the familiar feel of a desktop environment while maintaining the speed and responsiveness of the pure window manager. Its small footprint and minimalist approach makes it great for older, less powerful hardware -- but it is full-bodied and functional enough that many choose to use it on machines that can easily handle other desktop environments. The desktop aims to be functional, attractive, light on system resources, and adhere to the specifications proposed by Freedesktop participants to maximize interoperability.

Today, after two years of development, Xfce has officially released the 4.6.0 version of the desktop environment. Some notable new features include "out of the box" hibernate and suspend functions, a newly re-written sound mixer that leverages gstreamer to support multiple sound cards and configurations, and improvements and enhancements to the Thunar file manager.

Via OSNews comes word that the developers bringing Chrome to Linux have opted to use GTK over Qt as the browser's framework.

The development team's decision wasn't an easy one. The questions they addressed about Chrome's appearance and behavior, what end-users need and expect, and how to make it work smoothly on the Linux desktop are highly subjective, and in some cases, emotionally charged. The FAQ on the Chromium developer's site states that while both toolkits are capable of doing the job (WebKit handles most rendering with the exception of some form controls and dialogs), the team opted for GTK due to their level of familiarity with it.