On 2026-01-07 06:14, Michael J Gruber wrote:
Yes, and that was also because we (the gcc team) were all away for the
bulk of those two weeks and were not in a position to support any
breakages. I do hope the next year-end schedule is a bit more mindful
of this.
Schedules don't have minds - people do, ideally.
If I read the above correctly, the logic was:
- We don't have time to support breakages, so we don't want to have
breakages.
- We tell people not to build in the side-tag, consequently we have no
breakages.
We made the toolchain deadline, hooray!
While "no builds => no breakages" sounds ingenious, it defers all
problems to after the side-tag merge. It may or may not be that that's
the intention of the toolchain deadline.
At the time that the deadline was added[1] I brought up the issues the
lack of time would cause and things have turned out pretty much the way
we anticipated. FWIW, specifically from that FESCO issue:
```
Once the compiler package is updated, we'll have about a week for
interested parties to test and possibly deal with any FTBFS. We'll see
how it works out in practice. But I think that that it's better to start
with this small step for which we have general agreement that it is a
step in the right direction.
```
which means this is essentially the week in which we do this. If this
seems too cumbersome, we could try some variations next year within
these constraints, if the constraints aren't going to change.
It may actually work this way, but only if only one party is doing that.
As soon as we have two changes, picking breakages apart and resolving
them will be tedious. That's why we have side-tags in order to isolate
the effects of different changes.
Maybe for F46 we could try allowing Ada packages to build into the early
side tag and live with breakages if we can't get to them. It has the
risk of breaking all of the prebuild task[2] that runs during the
holidays and thus preventing *any* earlier feedback though.
Sid
[1] https://pagure.io/fesco/issue/3347
[2] https://copr.fedorainfracloud.org/coprs/siddhesh/mbp-gcc-16/
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
