As I tell everyone else- don’t trust their releases.
Nothing else is.
But at the same time, F/OSS has transformed into a loss leader for FAANGM monopolies, which coincides neatly with the timeline presented.
Here's the bugtraq event about it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018191
Does any of this make sense to you? Nobody who looks in the changes file has any idea the last three releases involved CVE issues. Not only are they purposefully obscured, the release itself contains undocumented bogus parser changes that were papered over during candidate voting.
1/ report the Google Fuzz Report to the actual development team, to coordinate and collaborate on a solution.
2/ not take three whacks at a security release just to fix the same vulnerability
3/ not attempt to ship whimsical patches in a security release
4/ not patch the test suite to lie to voters about the viability of a release candidate.
5/ ship a hotfix immediately after users report the bugs on 2.17
I'm not sure if that's the case, but that what's coming across. Small-minded pettiness.
Seeing these kinds of stories and interacting with the type of people who have them brings to mind an old saying:
“If everyone you meet is an asshole, you’re the asshole”
Note that I’m not saying that’s the case here or insulting you, that’s just the saying.
This story is filled with what seems like (at best) “personality conflicts” and your very dim view of essentially everyone involved in it with the exception of yourself.
It even ends with you essentially calling yourself Superman.
I’m not sure what the point of this is (vent? warning?) but it doesn’t read like a sympathetic and even remotely balanced telling of events, that’s for sure.
It may be worth reflecting on what you may have contributed to this if your goal is reducing the chance of repeats.