[Kde-imaging] Digikam + Kipi + Export and/or Sync to web services (and other such stuff)
anaselli at linux.it
Wed Oct 29 10:42:07 CET 2008
martedì 28 ottobre 2008 alle 21:09, Colin Guthrie ha scritto:
> There is definitely (IMO) scope for rebasing the whole KIPI API on top
> of Akonadi but this is perhaps something that is best left for a future
> occasion. Perhaps not, as I know the API breakage is up for discussion,
> but I don't want to bite of more than can be comfortably chewed at the
There's no big problems in breaking on trunk, untill kde 4.2 freeze time.
The discussion about api/abi breakage i'd like to have during kde code
sprint concerns on the stable branch and during beta/rc phase, having
attention to stable distros, e.g. the ones who want to use our packages.
I mean i don't like to think we have to implement every time new
functionalities during beta/rc, i'd expect more to stabilize the code instead.
Moreover we can't base our work always on trunk, as far as our final product
concerns. Maybe I'm wrong, but i can see the mess digikam does on mandriva
2009.0. It is almost unusable and to get new betas we need to backport
things from kdegraphics trunk, that's ok for developers not for final users.
So more attention to stable distros should be taken IMHO.
I don't mean we don't have to add new features of course, but maybe we
should work on branches once we have a beta out, and going on trunk for
future releases. Of course it's a nonsense (always imo) releasing a new stable
based on kdegraphics trunk since it has not been released yet....
My 2€ cents.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20081029/7320a4aa/attachment.sig
More information about the Kde-imaging