[Nepomuk] Exception for Dolphin - KFileMetadataWidget

Vishesh Handa me at vhanda.in
Sun Dec 23 15:21:36 UTC 2012

On Sun, Dec 23, 2012 at 8:01 PM, Frank Reininghaus <frank78ac at googlemail.com
> wrote:

> I agree with Sebastian - the freezes are there for a reason. I
> appreciate all offers to help with testing in the remaining time until
> the 4.10.0 release, but if that was really enough to make sure that
> there are no regressions, then we could just drop the betas and
> release a single RC in the future.

That's making a very generalized statement, and ignoring the current
situation. Please look at how much the code has changed from the 4.9. I'm
not advocating shipping something written from scratch this late into the

> However, past experience shows that
> the user feedback that we get for the 4 unstable releases before each
> 4.x.0 release helps to find many annoying bugs, but is still not
> enough to prevent that a few regressions make it into 4.x.0. Yes, we
> do have 4.x.1 and further bug fix releases, but in the end, users just
> don't like it when there are new bugs in 4.x.0, and I perfectly
> understand that.

Users always dislike bugs. We all understand that.

> The angry bug reports would end up in my inbox, and
> the reporters would even be right because I would be responsible for
> any problems if I approved the use of code that has not seen any wide
> testing before RC 2.

That's for the general case.

You have to look at exactly what I'm proposing and how much the code has
changed. The answer is not much.

I understand that almost all code have bugs, but you should at least look
at the uses cases of this widget, and if my patch satisfies all of the use
cases you can think of.

> Therefore, I think that using the new widget in Dolphin should not
> happen before KDE 4.11. Users who really want to use it earlier can
> just build Dolphin from source and apply the patch (which is not that
> hard even if you do not use a source-based distro, just install the
> kdelibs headers and then perform a few simple steps).

This rules out about 99% of the users.

I also thought again about Vishesh's argument that he would "have to
> spend 2-3 days (maybe even more?)" if we do not use the new widget in
> KDE 4.10, and I must say that I do not understand this at all. How can
> can using the old widget in KDE 4.10 make the user experience worse
> than in KDE 4.9 if he does not spend 2-3 days hacking on the old code?

You loose consistency. If a file is now indexed by Nepomuk it will show
different metadata in the Information Panel than if the file was not
indexed, and the user selected the file.

Current bugs visible via the KFileMetadataWidget -

* https://bugs.kde.org/show_bug.cgi?id=257438 (crash)
* https://bugs.kde.org/show_bug.cgi?id=270739 (crash)
* https://bugs.kde.org/show_bug.cgi?id=270739 (crash)
* https://bugs.kde.org/show_bug.cgi?id=281342 (crash)
* https://bugs.kde.org/show_bug.cgi?id=160157
* https://bugs.kde.org/show_bug.cgi?id=285039
* https://bugs.kde.org/show_bug.cgi?id=311796
* https://bugs.kde.org/show_bug.cgi?id=303875
* https://bugs.kde.org/show_bug.cgi?id=311201

Some of these bugs are already fixed in nepomuk-core. Other bugs can easily
be fixed in nepomuk-core and be properly tested. They cannot be properly
tested in kdelibs/nepomuk. The code base is too different now, and it would
require too much effort.

> Best regards
> Frank
> _______________________________________________
> Nepomuk mailing list
> Nepomuk at kde.org
> https://mail.kde.org/mailman/listinfo/nepomuk

Vishesh Handa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20121223/33889183/attachment.html>

More information about the release-team mailing list