I would like to learn from others: how do you handle security with testing? I like debian testing very much, and occassionally I have the idea of using this in production, too, but I fear the responsibility to take care of many security fixes on my own. here are the high-urgency vulnarable sources for testing:
https://security-tracker.debian.org/tracker/status/release/t...
but even more surprisingly, this list for stable is even longer:
https://security-tracker.debian.org/tracker/status/release/s...
Can anybody explain this?
(Yes, I will take the shame on me and ask this on a debian mailing list, however, maybe anybody has a good explanation here...)