Luca Beltrame composed on 2015-03-25 07:51 (UTC+0100):
...my killfile...... ... Heck, did you even *try* Plasma 5?
The answer to that appeared in your identical subject opensuse-kde thread http://lists.opensuse.org/opensuse-kde/2015-03/msg00044.html at http://lists.opensuse.org/opensuse-kde/2015-03/msg00048.html Had the roles been reversed, I would not have needed to ask. I don't killfile people, only subject strings. Had you followed through on my thread post you just replied to, you could have seen that I spent enough time with it since then to result in 4 bugs.kde.org comments over the past 4 days in addition to multiple postings on at least 3 mailing lists on KDE subjects since these twin threads started.
Did you even read the mail that started the thread, like many other people I asked to?
I read the original sent to opensuse-kde shortly after it arrived, also whatever bits of it were quoted in every reply as your repeat in opensuse-factory thread proceeded, and again before prior send the opensuse-factory original you sent on the 12th, one of rare original thread posts I ever intentionally kept longer than a few days that was not written by myself. My focus has been on your "- Checking for missing functionality".
Where are the bits that you define "betaware"? What doesn't work? What does? Are there obvious issues in packages? Or there are critical bugs that need to be reported upstream (you *would* report them, wouldn't you?)?
Answers to some of those were in the the part of my post you just replied to that you didn't quote or respond to. That part of my post was intentionally kept short, because longer would have been more repeats of what others have pointed out, and more repeats about more bugs long ago reported yet remaining unfixed, if even acknowledged via confirmation.
It also takes work to file good bug reports, reports that stand a reasonable chance of being acted upon. Not the least of it is getting in
It's better than NOT doing so and complaining.
I have filed KDE bugs[1], last month even[2], but I put considerable effort into not filing new bugs about previously reported behavior, which keeps my reports filed count low. Instead I CC and/or add a comment and/or a screenshot. KDE is a poor place to file bugs that you want to observe results from directly, if at all. Even when you file one for which you eventually see results, likelihood to see the bug touched at all by other than other users reporting similar experience by adding a comment, or putting themselves on CC is poor. Seeing your own bug marked resolved or even confirmed comes as a surprise to a mere mortal, non-progammer user.
installing, and only then seeing what happens. Filing a good bug means making a reasonable effort to not duplicate an existing bug, participating
That's why we asked the community, because we can't do all of this ourselves.
It's a wasted effort to invest energy with part of a community that has *no* intention of helping.
If I had no intention of helping, no one would find me saying anything at all here, or on bugs.kde.org, but the fact is I do appear both places, because I do want to see the new "stable" K made at least as good as the stable K it's supposed to replace. To me "as good as" means restoring missing functionality is more important than creating new functionality. Learning something new is fine, if it's something added that doesn't interfere with things old. It's not OK if it's made necessary because of the whole project having been and still being rewritten from scratch and the missing function hasn't been gotten too yet. Oh, you can't do that yet doesn't fly here. I'd really rather say I use the latest K* because it's the best K*, and recommend it to and install it for others; to need familiarity with only one version instead of trying to keep straight which one does what that the other doesn't. KDE4 never got to that point. I can't see KF5 even close to there for 13.3 either. That doesn't mean I don't wish the contrary, or won't be doing anything to that end. ...
this is not helping, and in fact it's tremendously demotivating.
Good you understand the concept of demotivation. It works both ways. Try putting yourself on the side of users who do test and do file bugs to mostly see the effort that went into them produce no apparent results. Seeing new features show up while old bugs lie fallow is tremendously demotivating too. [1] https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=NEEDSINFO&bug_status=ASSIGNED&bug_status=REOPENED&email1=mrmazda%40earthlink.net&emailassigned_to1=1&emailreporter1=1&emailtype1=exact&field0-0-0=bug_status&field0-0-1=reporter&list_id=1235081&type0-0-0=notequals&type0-0-1=equals&value0-0-0=UNCONFIRMED&value0-0-1=mrmazda%40earthlink.net [2] https://bugs.kde.org/show_bug.cgi?id=340248 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org