[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: FW: [REMINDER] Upcoming KDE 4.0 Milestones + Nepomuk
From: Allen Winter <winter () kde ! org>
Date: 2007-04-11 17:51:07
Message-ID: 200704111351.07508.winter () kde ! org
[Download RAW message or body]
On Wednesday 11 April 2007 12:35:57 pm David Faure wrote:
> On Wednesday 11 April 2007, Andreas Pakulat wrote:
> > On 11.04.07 17:27:18, Sebastian Trüg wrote:
> > > On Wednesday 11 April 2007 15:18:44 Dirk Mueller wrote:
> > > > On Tuesday, 10. April 2007, Aaron J. Seigo wrote:
> > > > > > I'll take a look on this in the next two weeks but it would be nice to
> > > > > > make it optional until 4.1.
> > > > >
> > > > > this would realistically mean application integration in 4.2 or later.
> > > >
> > > > No. There can be applications making use of nepomuk by 4.1, and then we can
> > > > include a polished and tested version of it in kdelibs for 4.1.
> > > >
> > > > if we put nepomuik into kdelibs for KDE 4.0, then we have to stay
> > > > compatible with it (also binary compatibility).
> > >
> > > that is actually a good point. So far not many people besides me have used the
> > > API for real. That is not the best situation for an API freeze.
> >
> > Well, in the thread on the release-team list it was said that a binary
> > incompatible 4.1 release is not completely out of question.
>
> Binary incompatible doesn't mean source incompatible though. If the API isn't mature
> enough, then even source compatibility might be an issue.
>
> But where to put it meanwhile is a problem indeed; who uses nepomuk currently, or plans to use it?
>
kdesupport? alongside strigi sorta makes sense to me.
-Allen
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic