Backwards compatibility of kdelibs/experimental

Sune Vuorela nospam at
Tue Dec 8 18:24:18 GMT 2009

On 2009-12-08, Thiago Macieira <thiago at> wrote:
> --nextPart2224014.W10Z83oVGD
> Content-Type: Text/Plain;
>   charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Em Ter=E7a-feira 08 Dezembro 2009, =E0s 16:08:43, Lubos Lunak escreveu:
>>  Hello,
>>  I have a question of about backwards compatibility of KNotificationItem
>>  and kdelibs/experimental in general and I don't mean just API. API is
>>  simple, there is no guarantee, but I don't see anything about the rest in
>> .
>>  For example, KNotificationItem from 4.3.x does not work in 4.4.x workspa=
> ce
>> (the D-Bus name has changed). Fortunately, there is still the old systray
>> mechanism, so there's no big loss of functionality as long as the old
>>  library is still around. And yes, there are apps outside of KDE SC that
>>  use it.
>>  Is it acceptable that something like that no longer works, and regardless
>>  of the answer, could it be added to the wiki page?
> Binary/behaviour compatibility includes D-Bus interfaces. So renaming an=20
> interface, removing methods, etc. is not BC.
> Anyway, this was an experimental lib. The D-Bus protocol should also be=20
> considered experimental there.

I don't think that actually breaking things should be allowed. In this
case, things doesn't really break as there is the fallback to the old
systray mechanism.

But if KDE4.3 apps didn't have access to the KDESC4.4 systray in any
way, I would consider it wrong, and something I think we should document
shouldn't be done.


More information about the kde-core-devel mailing list