On Freitag, 10. Januar 2014 11:28:34 CEST, Sebastian K=C3=BCgler wrote:=
=0A=0A> with the long =0A> term support workspace out, so we can recomm=
end people to use =0A> that, if they're slightly more adventurous, run =
4.13=0AI'm not sure whether I understand that - afaiu there will be no =
workspace > 4.11 ever, but other parts (baseapps) etc. proceed - and ne=
pomuk/baloo crosses those releases.=0A=0AIe. you'd tell them to=0A- sta=
y with workspace 4.11.x (x being the release right before the change to=
 baloo) and nepomuk and also all other packages of that time (eg. 4.12.=
4), iow. simply stop updating at all or to=0A- stay with workspace pre-=
baloo and only update other parts to baloo versions, what will likely c=
reate a mess in the semantic desktop stuff or to=0A- just update as usu=
al, accepting a potential friction (for clients/features "relying" on l=
ost nepomuk)=0A=0AIe. to either stop updating or be prepeared for migra=
tion trouble on the semantic desktop front.=0A=0AI think what Christoph=
 wanted to say was:=0Aplease don't start baloo like what ended nepomuk.=
=0A=0A=0A> Communicated in the right way=0A=0AMy 2=C2=A2?=0AAssuming yo=
u want to replace nepomuk by baloo in SC4:=0A =0A   Draw a fat red line=
.=0A=0APublically announce *now* that the sematic desktop system will g=
et an internal update that will preserve general functionality, but is =
unfortunately incompatible with the present nepomuk approach.=0AThis wi=
ll happen with [release here] in about [n] weeks, what implies to rathe=
r skip that particular version for productive systems - if you rely on =
semantic desktop features.=0A=0AThis was decided to happen now, because=
 KDE SC 4 will continue to be the "stable" KDE desktop environment for =
[estimated time here] and the semantic desktop either needs a major ove=
rhaul or is best not used at all, ie. the alternative would have been t=
o schedule this for KF5 & PW/2 and declare the "fix" for semantic deskt=
op issues to not use a semantic desktop.=0A=0AThere'll be migration too=
ls, but every further KDE SC release will not provide *any* support for=
 nepomuk anymore (beyond ABI compatibility library stubs)=0AIf you cruc=
ially rely on a clients nepomuk features, you can check [wiki url] to s=
ee whether it's already available in a baloo version - otherwise do not=
 update KDE SC beyond that version until it is.=0A=0AContrary to other =
suggestions i can also only recommend to ditch "nepomuk" as name to not=
 leave any ambiguity.=0AAccording to the reasons mentioned in this thre=
ad ("most hated"), the name is burned anyway, but the main reason is th=
at ppl. talk about semantic desktop features by the term "nepomuk" and =
that will lead to confusion since (if) you cut "legacy" nepomuk support=
 ("nepomuk is running, but does not work in client xyz")=0ASo communica=
te that nepomuk (and support for it) goes, baloo comes, the semantic de=
sktop idea stays - just without virtuoso.=0A=0APublish eg. an interview=
 with Vishesh that outlines the major differences between nepomuk and b=
aloo and the major benefits of this change.=0A=0A=0A=0ACheers,=0AThomas