this post was submitted on 27 Feb 2024
228 points (93.2% liked)
linuxmemes
24384 readers
722 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. 🇬🇧 Language/язык/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.