On Thu, Dec 12, 2019 at 9:59 AM Troy Dawson <tdawson@redhat.com> wrote:

I've had the night to sleep on it, and I now see that you are totally right.
I was getting so excited about the ability to always have a newer KDE
on RHEL, that I forgot the reason I run RHEL and it's clones in the
first place ... stability.

On the other hand, particularly when it comes to desktops/workstations, one of the problems with RHEL and the clones is you end up unable to run the software you want because the outside desktop software ecosystem has move too far forward after about 3 years let alone the full length of support for those releases (as there is in a way an acknowledgement from Red Hat on this issue, where they now provide newer compilers and associated stuff on the side to reflect the reality that compilers/languages are moving at a much faster pace than when RHEL had its first release).

So as a user, I think the first question is perhaps what sort of KDE experience do the people willing to do the work to make it available on RHEL want to provide.  If you want to make it stay at the same release as when first offered, then RPMS might provide the best/easiest solution to make it available.  On the other hand, if you either want to keep it up to date or use a 2 or 3 release cycle, then perhaps the module route might be more appropriate given that some key things are controlled by Red Hat.