On 2025-02-10 18:39, Neal Gompa wrote:
On Mon, Feb 10, 2025 at 6:21 PM Fabio Valentini <decathorpe@xxxxxxxxx> wrote:
On Mon, Feb 10, 2025 at 11:48 PM Tom Rix <trix@xxxxxxxxxx> wrote:
I am glad the gcc change came in before the branch.
But I would rather it have come into rawhide after the branch so the last weeks before the branch could have been spent on testing for F42 rather than scrambling to kludge/fix a lot of #include <cstdint>'s
Getting new GCC into rawhide *after* the branch point would mean
shipping GCC updates one release / 6 months later though - and I don't
think we'd want to do that, either.
Right. In an ideal world, it would land in Rawhide before the holidays.
Yes, that's kinda the effect I'm hoping to achieve with us publishing
untriaged/partially triaged results from the mass-prebuild in December.
We won't land gcc in rawhide and break everything at once, but we'll get
the equivalent benefit, i.e. early awareness.
Thanks,
Sid
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
