Thanks @aunoor for the post on this important topic. I will be looking at your post as we work on the transition to Plasma6.
Currently the OM contributor group is hard at work on the next release of ROME which will have both Plasma5 and Plasma6 packages and ISOs. Soon after we will have the next Rock release also with P5 and P6. After that we begin work on the complete transition to Plasma6. We will at that time be removing Plasma5 packages from Cooker repositories and in Cooker working to make the next ROME and Rock upgrades as trouble free as possible. The usual work flow is:
Cooker>ROME>Rock
Personally I can not wait for us to get rid of Plasma5. Not because I do not like it but because, IMO, right now we have to much to maintain and test.
Of course we never have enough testers but that is a separate issue.
My hope is that when we do go to all Plasma6 the user will just do a normal distro-sync or dsync like:
sudo dnf --refresh dsync --allowerasing
sudo dnf autoremove
Also where some Linux distros are offering P6 only with Wayland OM is offering P6 with Wayland and X11. We believe this is an issue of responsibility to users with older hardware. It does add to the workload in package building and our testing. For the same reason, to benefit users with older hardware, we have attempted an increase in focus on the LXQt desktop. I believe our LXQt is substantially better than it was a year ago. However I am a biased observer.
Note: We reccommend that Cooker and ROME users use dnf dsync to upgrade their systems rather than dnf up. This is because of frequent changes to distro-release-repos-pkgprefs. dnf dsync reads that and upgrades the system accordingly whereas dnf up simply upgrades to what it thinks is the numerically highest package version. This matters. Rock, by design, almost never sees any changes to distro-release-repos-pkgprefs.