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.
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.
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.
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).
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?
Best regards
Frank
_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk