Felix Miata wrote:
How much is much? "Much improved" is just hyperbole if the improvement isn't enough to get it across the threshhold from clearly betaware into good enough to do that which was previously both possible, and depended
I've removed your address from my killfile just this once to reply. Did you even read the mail that started the thread, like many other people I asked to? This is *not* constructive. 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?)? If you keep this generic, this is not helping, and in fact it's tremendously demotivating.
upon. Lots of fixes and feature additions can make anything look "much improved" compared to an immediately previous incarnation, but what counts
Power management is no small feat and changed considerably, for the better, in the 5.x codebase.
History tells us that the KDE4 team caused huge displeasure and
Feel free to keep KDE3 if you want, it's not maintained by the KDE team anyway. But don't ask *us* and I mean the team, to supplement upstream once LTS support for 4.x ends. Heck, did you even *try* Plasma 5? (and btw, our current relationship with upstream is quite good, and we even managed to fix some things ourselves in the past)
KDE3, as well as commitment to keeping KDE3 in openSUSE useful long past when upstream support ended.
We (as in the openSUSE community KDE team) do not *want* this commitment. We aren't enough and we all have other commitments to do. Especially since critical bits of the architecture Plasma 4.x depends on (like QGraphicsView) are essentially on permanent maintenance mode from Qt.
From user perspective, those are distinctions without differences. Users
Oh? Are you sure about that? You can run KDE applications in LXDE, GNOME, MATE. lxqt is using bits of the KDE Frameworks 5 (the libraries) and it's not even a KDE project. KDE is the community which makes software. The workspace, libraries, and applications are totally decoupled from each other. That's why making this migration is easier than if it weren't. And this is not news, it's been *years* in the making (and communicated from upstream, even).
That's an unfortunate plan, resulting from the practicalities of coupling grandiose intent with less than adequate resources to fulfill that intent
Felix, I wish you'd stop being so condescending. How are *your* contributions *here* helpful? How are you actually *helping* in any way at all? The resources come from the community. Aren't we all in this? Or do we want again a "us vs them" mentality even when there aren't any SUSE employees in the team?
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.
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. I'll say it again: no more discussion next time. Changes will come from top to down. It's a wasted effort to invest energy with part of a community that has *no* intention of helping. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org