Both of you misunderstand the point of Debian’s stability.
When I run Debian Stable I want to be sure nothing changes about how the system works, until I have time to plan an upgrade.
So KDE6 could have literally zero bugs and it still wouldn’t make sense to push it into a current Debian release, because it has new features.
I think backwards compatibility is the keyword here. That would be the biggest requirement to allow updates.
New bugs, and maybe for example new hardening policies needed, could be another one. Maybe a future firefox implements feature x and you want to / have to disable that.
But at the same time Firefox is the best example of upstream doing the versioning. They know when to freeze features and likely backport every security critical issue. Thats not the case with many other packages debian ships, where it just doesnt ship updates whatsoever.
Plasma 6 is the most tested release EVER. There where at least 5 ways to test it, there was KDE Neon and a dedicated atomic Fedora image for it.
There are many bugs only fixed in Plasma 6.
So it is debateable
Both of you misunderstand the point of Debian’s stability.
When I run Debian Stable I want to be sure nothing changes about how the system works, until I have time to plan an upgrade.
So KDE6 could have literally zero bugs and it still wouldn’t make sense to push it into a current Debian release, because it has new features.
I think backwards compatibility is the keyword here. That would be the biggest requirement to allow updates.
New bugs, and maybe for example new hardening policies needed, could be another one. Maybe a future firefox implements feature x and you want to / have to disable that.
But at the same time Firefox is the best example of upstream doing the versioning. They know when to freeze features and likely backport every security critical issue. Thats not the case with many other packages debian ships, where it just doesnt ship updates whatsoever.