On 10/22/20 5:06 PM, Jeff Law wrote:
On 10/22/20 6:53 AM, Neal Gompa wrote:
On Thu, Oct 22, 2020 at 8:27 AM Aleksandra Fedorova <alpha@xxxxxxxxxxxx> wrote:
Hi, all,
this is the informational message, no action required.
Upon agreement between gcc maintainers and ELN SIG we would like to
switch ELN buildroot to use GCC11 ahead of Fedora Rawhide.
Though ELN is defined as the buildroot where Fedora Rawhide code is
rebuilt into EL-like environment, in the ELN proposal we also
mentioned that ELN can be used to test certain buildroot-related
features on the side so it doesn't block Fedora Rawhide development.
We think that GCC11 is one such feature, where we can benefit from
testing it first on a small subset of the Fedora content in a separate
environment.
We would like to invite everyone to join this effort.
The work is currently tracked on Github:
https://github.com/fedora-eln/eln/issues/8
Once GCC11 is merged to the eln tag in koji, one would be able to use
it via, for example, mock or container environment:
quay.io/fedoraci/fedora:eln-x86_64
For more info on ELN please refer to ELN Docs (as soon as I update
them, which hopefully happens later today):
https://docs.fedoraproject.org/en-US/eln/
Why are you not just doing this in Rawhide? I feel like we've been
screwed now because the whole point was that ELN branches weren't
going to exist, and now we have one in the most important package!
From a timing standpoint we're trying to get ELN up and running with
gcc-11 right now. The earliest Jakub was comfortable dropping gcc-11
snapshots into rawhide was after stage1 development closes for upstream
gcc (mid-Nov) and even that probably needs to be discussed with FESCO
and the wider Fedora dev community as it is potentially disrupting
(regardless of how much testing and fixing I've already done in rawhide
in preparation for gcc-11). Delaying gcc-11 into ELN would throw
everything downstream of that off from a scheduling standpoint.
But I very much agree that GCC should be moving into rawhide earlier
than has been done in the past. In an ideal world it would have gone in
just after F33 branched and updated regularly.
Big +1 on that.
Right after branching rawhide tends to be relatively quiet as the just
branched version gets most of the attention, so any mishaps are fairly
contained and cause minimal disruption, but there's always enough going
on that you do get plenty of testing. And when the general focus starts
shifting back to rawhide and the next release, the worst initial kinks
have already been worked out.
That's how we try to land new rpm versions too, and it has proven to
work very well for all parties AFAICS. And whenever we miss that slot,
there's pain, suffering and lots of unnecessary stress.
- Panu -
_______________________________________________
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
