From what I’ve read, Kent expects others to just take his word for it, when he says his code wont break anything.
The kernel has long had practices around merging and releasing, specifically so that it no longer has to rely on contributors simply promising that their contributions have been tested and confirmed safe.
But Kent has repeatedly skirted or straight up ignored those practices.
This isn’t about not agreeing on code needing to be reliable. It’s about one person refusing to work with an established way of achieving that when contributing to an upstream effort.
He’s been told how to contribute again, and again, and again. And every time he takes it like it’s a personall affront to his credibility.
From what I’ve read, Kent expects others to just take his word for it, when he says his code wont break anything.
The kernel has long had practices around merging and releasing, specifically so that it no longer has to rely on contributors simply promising that their contributions have been tested and confirmed safe.
But Kent has repeatedly skirted or straight up ignored those practices.
This isn’t about not agreeing on code needing to be reliable. It’s about one person refusing to work with an established way of achieving that when contributing to an upstream effort.
He’s been told how to contribute again, and again, and again. And every time he takes it like it’s a personall affront to his credibility.