libgda/libgnomedb 1.0.0 are now packaged and ready to go. Just waiting on
the GNOME Office 1.0 release announcement. There hasn’t been almost any
change from 0.99.0, apart from a bug fixed by Akira and a little bit more
of API documentation (something we should work hard for the upcoming 1.0.x

Now that we’ve got 1.0 out, I think it is time to ask for their inclusion
in the development platform. Of course, following the GEP procedure :-)
One of the things we’re going to start doing, regardless of whether they
are accepted or not in the development platform, is to follow the GNOME
release cycle, which will avoid situations like having a 1.0 as delayed
as it’s been, and for no special reason. It’s clear that having 6 months
release cycles helps in concentrating on new features by little steps,
which is something that seems useful for GNOME-DB also.

Of course, the other important thing after 1.0 is getting Mergeant to
a 1.0 release also. Let’s see what comes up from Vivien’s refactoring.

And, last but not least, we need applications to use libgda/libgnomedb for
their data management. There are already a few
using them
, but we really need to have it more widely used.
Having GNOME applications use libpq (PostgreSQL client library), libmysqlclient
(MySQL’s), etc, is, IMO, a waste of time. If all apps used the same data
access/management API, we could benefit from a lot of integration, like
having the data sources used in MrProject available to Gnumeric/Abiword,
for instance. Also, a simple point of configuration
(gnome-database-properties) for all data sources
should help users a lot.


Spain lost the final against Lithuania :-(


Just installed the GNOME
2.4 Debian packages
, and so far they seem to work pretty well. I just had a few
warnings for some packages (easily fixed by dpkg -i --force-overwrite)
which contained files already in other packages.