Skip navigation.

GNOME 2.13.1 Development Release

Gnome 2.x
Gnome 2.x

Welcome to the latest issue of "The GNOME Development Releases". With
this issue, we start a new cycle (numbered 2.13) in which we will see
plenty of improvements, new features, bug fixes, speedups, etc. We
invite everyone to read (test?) this issue: missing an issue is like
missing your plane. Hrm. Maybe it's not a good comparison. Anyway, you
don't want to miss it, I assure you. Go download it. Go compile it. Go
test it. And go hack on it, document it, translate it, fix it.

For those not understanding the previous paragraph, this is our first
development release on our road towards GNOME 2.14.0, which will be
released in March 2006.

To compile it, you can use the jhbuild modulesets available at:
http://ftp.gnome.org/pub/GNOME/teams/releng/2.13.1/

bindings 2.13.1 statistics:
tar.gz: 18M total
tar.bz2: 12M total

desktop 2.13.1 statistics:
tar.gz: 157M total
tar.bz2: 111M total

platform 2.13.1 statistics:
tar.gz: 49M total
tar.bz2: 34M total

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of development code. Although it is buildable
and usable, it is primarily intended for testing and hacking purposes.
GNOME uses odd minor version numbers to indicate development status.

For more informations about 2.13, the full schedule, the official module
lists and the proposed modules list, please see our new shiny 2.13 page
on the wiki:
http://live.gnome.org/TwoPointThirteen

You can also check out the beginnings of the proposed modules list here which so far includes a lockdown editor, a game named Atomix, gnome-screensaver, fast user switching capabilities and the the deskbar applet

What would one diff the

What would one diff the ChangeLog/NEWS file against to show just the new changes? (The ChangeLog/NEWS files typically sent out with releases are automatically generated by diffing the versions of these files in the current tarball release against the tarball versions of the "previous" release). Polling every module author to determine whether the changes are with respect to 2.12.1 or 2.12.0 (or possibly even something different) would take far too much effort--plus would require someone writing the more versatile script and manually plugging in the relevant version numbers. Anyway, until someone comes up with a good solution to this problem, the initial release of development series will continue to come out without this information. Sorry. 2.13.2 will have it.