I took the plunge with my secondary system from KDE 5.24.6 → 5.25.5, and it was a step backwards. They’re also re-writing a lot of the code for animations and effects, and thus it loses much grace in day-to-day workflows and tasks. The experience was disappointing and felt like a meaningless “update” to a once glorious desktop environment.
So glad I stuck with 5.24.6 on my main system. 
I’m happy I made that decision.
No, on the contrary. See my post higher up — it wasn’t ready yet when I accidentally submitted it due to some stupid shortcut key in chromium. My updated post contains all the instructions. 
Updated post. Updated post… 
@Aragorn supposedly added something useful to the original post… should help us out… let’s see…
Blah, blah, blah… seems unimportant.
What else…
Repos? Sources? What? Lol… sounds like hacker stuff. Probably not important either…
What did he add to the post to make it supposedly helpful for us…?
Still looking… still looking…
OHHHHHHHHHHHH!!! That’s it!! The round of applause! THE TROPHY!!! THE FREE DRINKS!!! Ohhhh, bless you @Aragorn for the motivational emojis!
Now I know what to do! Life is so good once again! 
It’s missing a crucial step. The .zip archive file (plasma-5.24.7-LTS.zip) was never extracted, hence there are no packages to “add” using the repo-add command.
Perhaps this command can be slipped in, rather than the initial mv command? 
unzip /home/your-username-here/Downloads/plasma-5.24.7-LTS.zip -d ./
Optionally, an additional step to remove the large (no longer needed) .zip file, since mv is not used.
UPDATE: System fully updated and using KDE 5.24.7, via the local plasma-lts repo. 
Didn’t even need to reboot! (Disclaimer, I’m also using kernel-modules-hook, which is why I’m able to keep using the system without a hitch, even after a kernel update.)
Had to replace the mv line with the replacement unzip command, and everything else worked out smoothly. 
I want to give a special thanks to @philm for making this possible and creating the packages.
And to @Aragorn for the instructions and learning experience on adding your own local repositories.
But most importantly I want to thank all thirteen of my social media followers. Without your support these past 10 years, I wouldn’t be here today! We’re going to make it to the top one day! I PROMISE YOU. WE WILL MAKE IT TO THE TOP. 
Thank you, thank you, thank you for this!
Success was had!
NOW LET’S PARTY!
I believe with this you’ll even be able to downgrade back, right?
First and foremost, THANK YOU for this plasma update!!
Here’s a question that’s simmering around the noggin’ … Once I have completed this update, what will happen when the next plasma update comes along? Will we / should we re-enable the IgnoreGrp = plasma until the coast is clear again or will this plasma LTS update allow us safe harbor until the next plasma LTS update comes along?
AFAIK, because of the positioning of the [plasma-lts] section in /etc/pacman.conf it overrides the “Default” Plasma. So, I don’t think it’s necessary to remove it.
I know, but I realized this only after I had already gone to bed. I’ve updated my post now.
Don’t forget to like, subscribe and hit the notification bell! 
Normally you should be safe, due to the section for [plasma-lts] sitting above the [extra] section in /etc/pacman.conf.
That said, there is a possibility that @philm will be adding an official repo for Plasma LTS, given the new Manjaro-branded hardware that’s about to come out, and which may ship with the LTS instead.
So I was partially right when saying it should be safe due to its position.
And I was also right in saying this should allow you to upgrade to the previous version:
Even i don’t waste my time with plasma, happy for you all .
Dunno, d’you think so after upgrading to 5.25 without backing up my system(like a dumbass)?..? Good question that…
Timeahift is you friend. And I’ve only recently forced myself to meet him, and ma’an am I glad I did.
Back to your question, it may be safe. Maybe not. I expect the worst that can happen is you lose your desktop config and have to do it again. That’s why timeshift is your friend…
Now that’s silly. Own your 
Manjaro Team, nobody forced you to push it to Stable. Nobody has that power. It was decided by Manjaro Team. If Manjaro Team decides to push the update, because of a few newbies on the forum who are scared to switch branch, just own it, don’t put it on newbies back now.
Now if people in Manjaro team say, no don’t push to Stable, there are these issues blablabla, but someone overrides their call, then blame Manjaro Team as a whole, it is your failure, not the dozen forum users who asked for the update to reach Stable.
Maybe you need better process in Manjaro Team, maybe work on that internally so things get better in the future.
Yep, that’s true, I hadn’t thought about that actually… And, as I programmed TimeShift a week or so ago, who knows, I might give it a bash after all(but when I feel confident enough, of course, i.e I’ll have to work myself up to it…)! 
Exactly.
Imagine that everyone agreed to keep the branch stable with everything LTS-ish. Treating this strategy as an update policy for the branch could be more understandable for those who are in a hurry for new things. They could go to other branches if they didn’t agree with the update policy, which I believe, the way it is now, already works well for the majority of users.
In all fairness, I tend to agree with that point of view myself. Just my 2 cents
Indeed. That’s why it’s called the stable branch, after all.
But as with anything in life, it is the loudmouths, the people that makes the most noise, who’s voice will be listened to…
Thanks guys, I was even able to downgrade my KDE 5.25.5 to 5.24.7 using your local repo idea ! Many thanks, I’m glad I could get back to the LTS version, using pacman -Suu instead of pacman -Syu…
Cheers,
Eddy
Yes, downgrading is no problem, just did it and it went without a hitch. Just use sudo pacman -Suu instead…
Cheers,
Eddy
