[Tracker] Proposing a release



Hi all,

 We have been working hard last months, and now we have a tracker in a
stable state. I think it is so stable as to propose a release in a
couple of weeks.

 It could be tracker 0.6.90, and would include a completely refactored
daemon (splitted in two processes), introspection in the DBus API,
modules for the indexer, some new convenience methods in the API, some
documentation, initial support for playlists and a lot of other
improvements like unit tests (low coverage, but there they are), the
opportunity to build modules for the indexer out-of-the-tree and...
well, somebody should prepare proper Release Notes.

 Things like FTS and the decomposed tables schema should wait for the
next release. This changes are going to break the API completely, and
are so big and deep that justify a 0.7 version. I think a "last" release
in the 0.6.x series is necessary.

 Jamie: What do you think about this?

 The people in Rygel (previously GUpnp) are using tracker and to have a
new release would simplify a lot their life (at least in the
technological level). It can also help us to bugtriagging the current
bugs, and receive fresh feedback from regular users.

 The pending tasks for this release (if Jamie agree on it) are at least:

* Finish the save/restore of metadata between reindexes
* Better handling of removable devices

 So... comments?

Ivan Frade




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