On Sunday 03 of May 2015 19:19:55 Achim Gratz wrote:
Luca Beltrame writes:
Achim Gratz wrote:
How you suppose that this increases your chances of getting the feedback you seem to want is not clear to me.
After saying that some feature will be back in Plasma 5.3 and getting answers as "I'll believe it when I see it", I understood there was no point in asking.
....
The Plasma5 update you are planning to do is redefining Tumbleweed again, and in some ways destroys the original promise of "safe for daily work" completely. There is no way to go back and you even intend of forcing that big transition at a time that the user can not control (actually you can't control it either since it will come around when testing is complete). Sure, I can hold off on updates, but that's not going to work for long since I wouldn't be getting security updates either. Trying to lock KDE 4.x for a while on my own is an option, but of course if it breaks (the packages are no longer in TW as well, so no automated tests either) then you're going to tell me that I should update. If I update and things break you're going to tell me to file upstream bugs. Going back to 13.2 is also not really an option at this point in time.
IMHO, we have been quite conservative already in this regard. E.g. some other distros thought 5.2.x is good enough for default with their stable release, or at least for their beta releases. This is off course no measure at all, but just to give you an idea we are not pushing versionitis on users. The update itself indeed will require some adjustments to suit personal work habits, but that would be the case with 5.0, 5.3 or 5.55. If people are using rolling release i would expect them to not be surprised if a package update will require some manual labor at some point, and with rolling release they cannot predict, or schedule a vacation when will that happen. That there are some grave bugs for some users is also understood, but those will always exist with any software (heck, i hear rumors some still use KDE3), but all things considered (maintenance costs/time/motivation, features, bugs, support for 4.x workspace, etc...) the team has decided we move forward. Cheers, Hrvoje