First of all, I would like to mention that I'm using Fedora KDE since F23 or F24 and I had it installed for 4+ years without re-installation on my previous laptop, so I also lean towards Golboa's experience, rather than yours. But I understand your point and the reason for the existing schedule is pretty simple, as far as I understand it, while majority of the people who are using Fedora - Gnome users and Gnome and Fedora's schedule are perfectly aligned, giving a great focus and respective amount of time to polish Fedora's Gnome experience. KDE is a minority of Fedora's users, although it's a second most popular flavour (there was a statistics published few months ago), I believe it's about 7% percent (don't quote me on that) of all fedora users, compared to 70%+ for Gnome, hence it's ... hence ... for the lack of a better work, less polished at prioritized experience? There is actually a discussion item for tomorrows (today's) call of KDE SIG to align KDE and Fedora release schedule. Being said that, I can see a point why one would like to freeze a version of some package, but based on my personal experience, I'm not sure there is a problem that needs solving when it comes to the KDE Plasma specifically, empthesys on my experience. One the reasons I actually use KDE Plasma with Fedora is because I would prefer several package sets to be up to date as much as possible, that includes kernel, linux-firmware, DE (plasma in this case), mesa and application set (kf and kde-apps in this case). I think generally Fedora is doing an amazing job in keeping exactly those sets at upstream level. If there is actually a need for freezing packages, I actually like what Manjaro is doing with separation of [package] and [package]-git to get latest stable or THE latest packages, maybe Fedora can do something similar and provide package or DNF group if that's possible, because, you know, dependencies. Just wanted to provide my input. --- Best regards, Alex ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, January 3rd, 2021 at 22:42, Mikhail Ramendik <mr@xxxxxxxxxxx> wrote: > On Sun, 3 Jan 2021 at 10:24, Gilboa Davara gilboad@xxxxxxxxx wrote: > > > As a long Fedora and KDE user I usually don't enter such discussions, but nevertheless, I feel a response is in order. > > > > Following your own anecdotal experience and some random bug report you assume that your own personal experience is "regular occurrence" (your words, no mine). > > > > Let me share my anecdotal experience: I run a business on Fedora and CentOS. ~20 desktops and workstations (Most running Fedora/KDE) and far too many servers and VMs. > > > > Sure, I see breakage from time to time, but my experience couldn't be any different than yours. > > > > Heck, I'm typing this on an aging Xeon workstation that has been running Fedora/KDE since Fedora ~12-13 (!). > > > > Does my personal anecdotal experience negate yours, simply because I have more PCs? Nope. > > > > ... and this is the exact reason I avoid making broad generalizations. E.g. " breaking updates to KDE are kind of a > > > > regular occurrence"... > > CentOS is a very different beast from Fedora in this regard. The EPEL > > build of KDE uses the LTS version. > > My question is specifically about drops of new major component > > versions. I am trying to understand why the schedule is like this, > > beyond the matter of Plasma releases (as the problem I had was with > > Framework and not Plasma). > > New major component version drops are a bit of a lottery; I can well > > believe that for some people they always went flawlessly so far, but > > they are an inherent risk. If I could understand the schedule, perhaps > > I could come up with a mitigation strategy. > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Yours, Mikhail Ramendik > > Unless explicitly stated, all opinions in my mail are my own and do > > not reflect the views of any organization > > kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
