[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Status update for GNOME 2.24 and 2.26



Hi,

I posted a status update regarding the GNOME situation post the lenny
freeze to my blog, which is syndicated by Planet GNOME.

For those who have missed it, here is a text version.

GNOME 2.26 was released last week, and I couldn't help adding myself to
the long list of celebrating posts in Planet GNOME. Looking at the
release notes, it looks like this release adds a good number of very
visible features, and also keeps improving on ongoing transitions like
gvfs.

The Debian GNOME team is obviously not ignoring this fact and started to
work very hard on updating GNOME for squeeze as soon as the lenny freeze
was over.

First, the new versions of GLib and GTK+ were uploaded to unstable, and
managed to transition to testing very easily. The rest of GNOME 2.24
bits, which had been patiently waiting on experimental for months, has
been uploaded with care not to disrupt any of the many transitions the
Debian release team is currently dealing with. You can have a quick
glance at how things are going in our 2.24 status page, but the summary
is that most of GNOME 2.24 is in unstable, with a few notable exceptions
which are held back by ongoing testing transitions. Namedly,
evolution-data-server is trying to trickle into testing, which is in turn
holding the final bits: gnome-panel, nautilus and related packages, but
we think this will be over soon.

As soon as GNOME 2.24 is safe in squeeze, we'll immediately turn our
focus to the new GNOME 2.26 release. Our initial plan is to package the
trivial bits and leaf packages which can't break stuff for unstable, and
herd the more complex modules via experimental, to avoid breaking
unstable at all. There are some exceptions; we plan to keep gnome-session
2.22 in unstable/testing until 2.26.1 is released to avoid getting a
broken session saving in Debian.

People might wonder why we insist on hitting what would seem a dead horse
by first dealing with 2.24 and not 2.26 directly. The main reason is that
these packages had been ready for a long time, and were in good shape to
transition to testing quickly and with little pain. Preparing 2.26
directly would mean throwing away a lot of hours of packaging and
polishing effort, and it's not like we're releasing squeeze any time soon
anyway.

Enjoy the hopefully not too bumpy road to 2.26!


-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi@sindominio.net     jordi@debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


Reply to: