4 ms·
> makes breaking, unreviewed changes in kernel, And reverted them as soon as the issue became apparent. > then flames the maintainer who was working on cleanl
by josefx 1y ago
> makes breaking, unreviewed changes in kernel,
And reverted them as soon as the issue became apparent.
> then flames the maintainer who was working on cleanly updating the kernel for the not-yet-released compiler?
Talking aboutchanges that he had not pushed by the time Linus published the release candidate.
Also the "not yet released" seems to be a red herring, as the article notes having beta versions of compilers in new releases is a tradition for some distros, so that should not be unexpected. It makes some sense since distros tend to stick to a compiler for each elease, so shipping a soon to be out of maintenance compiler from day one will only cause other issues down the road.
- Kwpolska 1y agoFedora releases are supported for about 13 months after release. They could live with an older version of GCC for a year.
- Denvercoder9 1y ago> They could live with an older version of GCC for a year. That's just not what Fedora is, though. Being on the bleeding edge is foundational to Fedora, even if it's sometimes inconvenient. If you want battle-tested and stable, don't run Fedora, but use Debian or something.
- Kwpolska 1y agoBleeding-edge is fine, but shipping a beta C compiler seems a bridge too far. Even Arch does not ship GCC 15 yet.