Nacho_Trebuchet I stay to upstream stuff and hardly do any big changes, just do some Solus integration changes likes statelessness or theming stuff, which can be changes anytime.
We do not have everything piece of software which KDE project has, either I decide it's a great inclusion for our KDE repo or there was a package request. Just because it's the newest thing it's not gonna land inside the repo, or sometimes we cannot add it yet to the repo because we have some missing builddeps which cannot be changed because reasons (you can always ask me on IRC).
So in short, what you read inside the Changelog and we have in our repo you will receive as an update, I do not hold back packages (only when shit hits the fan with that update and I don't have any patches ready, like with 5.21.0 which had tones of issues on the base level which I did not feel comfortable to push and break stuff for the user just for the sake of having the latest greatest), and not automatically any new software they mention inside the blog post.