[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:       Sebastian =?iso-8859-1?q?Tr=FCg?= <strueg () mandriva ! com>
Date:       2007-04-11 15:27:18
Message-ID: 200704111727.19070.strueg () mandriva ! com
[Download RAW message or body]

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.

> only few applications should be affected by nepomuk - and thats why I think
> it makes sense to slip it for KDE 4.1.
>
> Just because its not in kdelibs doesn't mean applications can't make use of
> it. It just means its not part of 4.0. And thats great. Remember, there is
> life after KDE 4.0 (at least if we ever manage to release 4.0 instead of
> cramming every possible new feature in it (2nd version syndrome).

But where do we put it then so it gets attention? playground surely is a bad 
place. Maybe extragear-libs, but extragear is still in KDE3 mode...

Cheers,
Sebastian

PS: Sorry for the late reply, I was on an extended Easter-weekend without any 
internet connection (yes, there actually are remote places (in france) 
without ;)
[prev in list] [next in list] [prev in thread] [next in thread]